@rse/ase 0.0.56 → 0.0.58

package/plugin/skills/ase-code-insight/help.md

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-code-insight` - Project Insight
+
+##  SYNOPSIS
+
+`ase-code-insight`
+    [`--help`|`-h`]
+    *code-references*
+
+##  DESCRIPTION
+
+The `ase-code-insight` skill gives high-level *insights* into the
+project through the referenced source code. The skill produces four
+sections: a *PROJECT ABSTRACT* (summary derived from `README.*` or
+source scanning), a *PROJECT AUTHOR* list (from `git shortlog`),
+a *SOURCE CHURN* table (most-committed files in the last year), and
+a *MODULE STRUCTURE* Mermaid diagram of modules and their imports.
+
+##  ARGUMENTS
+
+*code-references*:
+    One or more file or directory references to source code that
+    should be inspected for insights.
+
+##  EXAMPLES
+
+Get insights into the current project:
+
+```text
+❯ /ase-code-insight src/
+```
+
+Get insights into a specific subsystem:
+
+```text
+❯ /ase-code-insight tool/src/
+```
+
+##  SEE ALSO
+
+`ase-code-explain`, `ase-code-analyze`, `ase-arch-analyze`.

package/plugin/skills/ase-code-lint/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-code-lint
-argument-hint: "<source-reference>"
+argument-hint: "[--help|-h] [--auto|-a] <source-reference>"
 description: >
     Lint source code for potential code quality problems.
     Use when the user wants to "lint" or "check" source code.
@@ -14,9 +14,6 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Lint Source Code
-================
-
 <skill name="ase-code-lint">
 Lint Source Code
 </skill>
@@ -27,11 +24,6 @@ Lint Source Code
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *analyzing source code*.
-</role>
-
 <objective>
 *Analyze* the code of `<getopt-arguments/>` for *potential problems*
 related to a set of code quality aspects.

package/plugin/skills/ase-code-lint/help.md

@@ -0,0 +1,54 @@
+
+##  NAME
+
+`ase-code-lint` - Lint Source Code
+
+##  SYNOPSIS
+
+`ase-code-lint`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    *source-reference*
+
+##  DESCRIPTION
+
+The `ase-code-lint` skill lints the source code of the referenced
+location for *potential code quality problems* related to a fixed set
+of code quality aspects. The investigation is dispatched to a
+sub-agent (`ase:ase-code-lint`) so that scanning details do not leak
+into the user-visible transcript.
+
+For each detected problem, the skill renders a unified-diff *SOLUTION*
+preview and either asks the user to `ACCEPT` or `REJECT` the proposed
+correction interactively or — with `--auto` — applies all corrections
+automatically.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically apply every proposed correction without asking the
+    user via the interactive dialog.
+
+##  ARGUMENTS
+
+*source-reference*:
+    A file, directory, or other reference to the source code to lint.
+
+##  EXAMPLES
+
+Lint a source file interactively:
+
+```text
+❯ /ase-code-lint src/server.ts
+```
+
+Lint a directory and automatically apply all corrections:
+
+```text
+❯ /ase-code-lint --auto src/handlers/
+```
+
+##  SEE ALSO
+
+`ase-code-analyze`, `ase-code-resolve`, `ase-code-refactor`,
+`ase-docs-proofread`.

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-code-refactor
-argument-hint: "[<task-id>:] <request>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--next|-n <option>] [<task-id>:] <request>"
 description: >
     Refactor Code Base:
     Use when user wants to refactor the code base.
@@ -17,23 +17,16 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Refactor Artifacts
-==================
-
 <skill name="ase-code-refactor">
 Refactor Artifacts
 </skill>
 
 <expand name="getopt"
     arg1="ase-code-refactor"
-    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    arg2="--auto|-a --dry|-d --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*.
-</role>
-
 <objective>
 *Refactor* existing artifacts the following way:
 <request><getopt-arguments/></request>
@@ -259,6 +252,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         the information from refactoring A<n/> and all derived realization
         decisions into it. Store the resulting task plan in <content/>.
 
+        If a `CHANGELOG.md` file exists in the project (or in any
+        affected sub-package), the plan *MUST* include, as part of its
+        `## ※ CHANGES` section, an explicit bullet point describing
+        the addition of a corresponding new entry to that `CHANGELOG.md`
+        file, aligned with its existing style and conventions.
+
+        <if condition="<getopt-option-dry/> is equal `true`">
+        You *MUST* completely omit the `## ※ VERIFICATION` section
+        (including its heading and all of its bullet points) from
+        <content/>.
+        </if>
+
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 
@@ -278,9 +283,26 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    5.  Directly pass-through control to the `ase:ase-task-edit` skill.
-        Set <args></args> (set args to empty). If <getopt-option-next/>
-        is not equal `none`, set <args><args/> --next
-        <getopt-option-next/></args> (append to args). Then call the
-        tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+    5.  Directly pass-through control to the next skill:
+
+        1.  <if condition="<getopt-option-next/> is equal `IMPLEMENT`">
+            Call the tool `Skill(skill: "ase:ase-task-implement")` to
+            *implement* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        2.  <if condition="<getopt-option-next/> is equal `PREFLIGHT`">
+            Call the tool `Skill(skill: "ase:ase-task-preflight")` to
+            *preflight* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        3.  <if condition="
+                <getopt-option-next/> is not equal `IMPLEMENT` AND
+                <getopt-option-next/> is not equal `PREFLIGHT`
+            ">
+            Set <args></args> (set args to empty).
+            <if condition="<getopt-option-next/> is not equal `none`">
+            Set <args><args/> --next <getopt-option-next/></args> (append to args).
+            </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            </if>
 

package/plugin/skills/ase-code-refactor/help.md

@@ -0,0 +1,74 @@
+
+##  NAME
+
+`ase-code-refactor` - Refactor Artifacts
+
+##  SYNOPSIS
+
+`ase-code-refactor`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    [`--dry`|`-d`]
+    [`--next`|`-n` *option*]
+    [*task-id*:] *request*
+
+##  DESCRIPTION
+
+The `ase-code-refactor` skill refactors existing artifacts by
+investigating the related code, internalizing refactoring tenets
+(Behavior Preservation, Boy Scout Rule, DRY, SRP, loose coupling,
+clear interfaces, ...), proposing one or more *refactoring approaches*
+with pros and cons, letting the user pick the preferred approach,
+and composing a corresponding *task plan*.
+
+The skill does *not* directly modify source files. It persists the
+plan via `ase_task_save` and then hands off to `ase-task-edit`,
+`ase-task-preflight`, or `ase-task-implement`, as selected by
+`--next`.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically pick the recommended refactoring approach without
+    asking the user via the interactive dialog.
+
+`--dry`|`-d`:
+    Compose the plan *without* the `※ VERIFICATION` section. When
+    `ase-task-implement` later applies such a plan, it strictly skips
+    the entire verification phase (no build, tests, linter,
+    type-checker, or program execution) once the source files have
+    been modified.
+
+`--next`|`-n` *option*:
+    Automatically choose the next step after composing the plan,
+    where *option* is either `none` (default, hand-off to
+    `ase-task-edit` interactively), `DONE` (stop), `EDIT` (hand off
+    to `ase-task-edit`), `PREFLIGHT` (hand off to
+    `ase-task-preflight`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+[*task-id*:] *request*:
+    Description of the refactoring *request*. Optionally prefixed
+    with a *task-id* followed by a colon to bind the resulting plan
+    to a specific task id.
+
+##  EXAMPLES
+
+Refactor a module into smaller files:
+
+```text
+❯ /ase-code-refactor split src/handlers.ts into per-route modules
+```
+
+Refactor under a named task and directly hand off to implementation:
+
+```text
+❯ /ase-code-refactor --next IMPLEMENT cleanup: extract HTTP client into its own class
+```
+
+##  SEE ALSO
+
+`ase-code-craft`, `ase-code-resolve`, `ase-task-edit`,
+`ase-task-preflight`, `ase-task-implement`.

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-code-resolve
-argument-hint: "[<task-id>:] <problem>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--next|-n <option>] [<task-id>:] <problem>"
 description: >
     Resolve Problem:
     Use when user wants a bug fixed or problem resolved.
@@ -17,23 +17,16 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Resolve Problem
-===============
-
 <skill name="ase-code-resolve">
 Resolve Problem
 </skill>
 
 <expand name="getopt"
     arg1="ase-code-resolve"
-    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    arg2="--auto|-a --dry|-d --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*.
-</role>
-
 <objective>
 *Resolve* the following problem:
 <problem><getopt-arguments/></problem>
@@ -307,6 +300,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         the success of the resolution, by using the <format/> defined for a
         task plan. Store the resulting task plan in <content/>.
 
+        If a `CHANGELOG.md` file exists in the project (or in any
+        affected sub-package), the plan *MUST* include, as part of its
+        `## ※ CHANGES` section, an explicit bullet point describing
+        the addition of a corresponding new entry to that `CHANGELOG.md`
+        file, aligned with its existing style and conventions.
+
+        <if condition="<getopt-option-dry/> is equal `true`">
+        You *MUST* completely omit the `## ※ VERIFICATION` section
+        (including its heading and all of its bullet points) from
+        <content/>.
+        </if>
+
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 
@@ -333,9 +338,26 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    6.  Directly pass-through control to the `ase:ase-task-edit` skill.
-        Set <args></args> (set args to empty). If <getopt-option-next/>
-        is not equal `none`, set <args><args/> --next
-        <getopt-option-next/></args> (append to args). Then call the
-        tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+    6.  Directly pass-through control to the next skill:
+
+        1.  <if condition="<getopt-option-next/> is equal `IMPLEMENT`">
+            Call the tool `Skill(skill: "ase:ase-task-implement")` to
+            *implement* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        2.  <if condition="<getopt-option-next/> is equal `PREFLIGHT`">
+            Call the tool `Skill(skill: "ase:ase-task-preflight")` to
+            *preflight* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        3.  <if condition="
+                <getopt-option-next/> is not equal `IMPLEMENT` AND
+                <getopt-option-next/> is not equal `PREFLIGHT`
+            ">
+            Set <args></args> (set args to empty).
+            <if condition="<getopt-option-next/> is not equal `none`">
+            Set <args><args/> --next <getopt-option-next/></args> (append to args).
+            </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            </if>
 

package/plugin/skills/ase-code-resolve/help.md

@@ -0,0 +1,81 @@
+
+##  NAME
+
+`ase-code-resolve` - Resolve Problem
+
+##  SYNOPSIS
+
+`ase-code-resolve`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    [`--dry`|`-d`]
+    [`--next`|`-n` *option*]
+    [*task-id*:] *problem*
+
+##  DESCRIPTION
+
+The `ase-code-resolve` skill resolves a *bug* or *problem* by
+investigating the related code, internalizing resolution tenets
+(Surgical Changes, No Cleanups, Minimum Flags, Code Adequacy, Origin
+Proximity, ...), proposing one or more *resolution approaches* with
+pros and cons, letting the user pick the preferred approach, and
+composing a corresponding *task plan*.
+
+The *problem* may also be given as a bare issue identifier (e.g. `P1`
+or `T1`) previously produced by `ase-code-analyze` or
+`ase-arch-analyze` and persisted in the `ase` MCP key/value store
+under `ase-issue-<id>`.
+
+The skill does *not* directly modify source files. It persists the
+plan via `ase_task_save` and then hands off to `ase-task-edit`,
+`ase-task-preflight`, or `ase-task-implement`, as selected by
+`--next`.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically pick the recommended resolution approach without
+    asking the user via the interactive dialog.
+
+`--dry`|`-d`:
+    Compose the plan *without* the `※ VERIFICATION` section. When
+    `ase-task-implement` later applies such a plan, it strictly skips
+    the entire verification phase (no build, tests, linter,
+    type-checker, or program execution) once the source files have
+    been modified.
+
+`--next`|`-n` *option*:
+    Automatically choose the next step after composing the plan,
+    where *option* is either `none` (default, hand-off to
+    `ase-task-edit` interactively), `DONE` (stop), `EDIT` (hand off
+    to `ase-task-edit`), `PREFLIGHT` (hand off to
+    `ase-task-preflight`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+[*task-id*:] *problem*:
+    Description of the *problem* to resolve, or a bare issue
+    identifier like `P1` or `T1` previously produced by an analyzer
+    skill. Optionally prefixed with a *task-id* followed by a colon
+    to bind the resulting plan to a specific task id.
+
+##  EXAMPLES
+
+Resolve a free-text problem:
+
+```text
+❯ /ase-code-resolve fix race condition in cache invalidation
+```
+
+Resolve a previously analyzed issue and hand off to implementation:
+
+```text
+❯ /ase-code-resolve --next IMPLEMENT P1
+```
+
+##  SEE ALSO
+
+`ase-code-craft`, `ase-code-refactor`, `ase-code-analyze`,
+`ase-arch-analyze`, `ase-task-edit`, `ase-task-preflight`,
+`ase-task-implement`.

package/plugin/skills/ase-docs-proofread/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-docs-proofread
-argument-hint: "<docs-reference>"
+argument-hint: "[--help|-h] [--auto|-a] <docs-reference>"
 description: >
     Analyze the documents for spelling, punctuation, or grammar errors.
     Use when the user wants to "proofread" or "spellcheck" a document.
@@ -14,11 +14,8 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Proofread Documentation
-=======================
-
 <skill name="ase-docs-proofread">
-Analyze the documents for spelling, punctuation, or grammar errors.
+Analyze documents for spelling, punctuation, or grammar errors
 </skill>
 
 <expand name="getopt"
@@ -27,14 +24,8 @@ Analyze the documents for spelling, punctuation, or grammar errors.
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level proofreader*, specialized in
-checking and correcting the *spelling*, *punctuation* and *grammar* of
-documents.
-</role>
-
 <objective>
-*Analyze* the documents of `<getopt-arguments/>` for problems in their
+*Proofread* the documents of `<getopt-arguments/>` for problems in their
 *spelling*, *punctuation*, or *grammar* and propose corrections.
 </objective>
 

package/plugin/skills/ase-docs-proofread/help.md

@@ -0,0 +1,54 @@
+
+##  NAME
+
+`ase-docs-proofread` - Proofread Documents
+
+##  SYNOPSIS
+
+`ase-docs-proofread`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    *docs-reference*
+
+##  DESCRIPTION
+
+The `ase-docs-proofread` skill analyzes the referenced documents for
+*spelling*, *punctuation*, and *grammar* errors and proposes
+corrections. The investigation is dispatched to a sub-agent
+(`ase:ase-docs-proofread`) so that scanning details do not leak into
+the user-visible transcript.
+
+For each detected problem, the skill renders a unified-diff
+*CORRECTION* preview and either asks the user to `ACCEPT` or `REJECT`
+the proposed correction interactively or — with `--auto` — applies
+all corrections automatically.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically apply every proposed correction without asking the
+    user via the interactive dialog.
+
+##  ARGUMENTS
+
+*docs-reference*:
+    A file, directory, or other reference to the documents to
+    proofread.
+
+##  EXAMPLES
+
+Proofread a single document interactively:
+
+```text
+❯ /ase-docs-proofread README.md
+```
+
+Proofread an entire documentation directory automatically:
+
+```text
+❯ /ase-docs-proofread --auto docs/
+```
+
+##  SEE ALSO
+
+`ase-code-lint`, `ase-meta-changes`.

package/plugin/skills/ase-meta-changes/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-changes
-argument-hint: ""
+argument-hint: "[--help|-h]"
 description: >
     Update changes entries in CHANGELOG.md files
 user-invocable: true
@@ -17,18 +17,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Update ChangeLog Entries
-========================
-
 <skill name="ase-meta-changes">
 Update ChangeLog Entries
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *Git version control*.
-</role>
-
 <objective>
 Help to complete, consolidate and sort *ChangeLog* entries of the most
 recent *ChangeLog* section, based on underlying *Git* commits and staged

package/plugin/skills/ase-meta-changes/help.md

@@ -0,0 +1,33 @@
+
+##  NAME
+
+`ase-meta-changes` - Update ChangeLog Entries
+
+##  SYNOPSIS
+
+`ase-meta-changes`
+    [`--help`|`-h`]
+
+##  DESCRIPTION
+
+The `ase-meta-changes` skill helps to *complete*, *consolidate*, and
+*sort* the entries of the most recent section of a `CHANGELOG.md`
+file, based on the underlying *Git* commits and the currently staged
+changes in the Git *index*.
+
+Each entry is formatted as `<prefix>: <summary>` where *prefix* is
+one of `FEATURE`, `IMPROVEMENT`, `BUGFIX`, `UPDATE`, `CLEANUP`, or
+`REFACTOR`. Entries are grouped and sorted by this prefix. The
+date in the section header is also updated to the current date.
+
+##  EXAMPLES
+
+Update the most recent ChangeLog section:
+
+```text
+❯ /ase-meta-changes
+```
+
+##  SEE ALSO
+
+`ase-meta-commit`, `ase-docs-proofread`.

package/plugin/skills/ase-meta-chat/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-chat
-argument-hint: "<llm> <query>"
+argument-hint: "[--help|-h] <llm> <query>"
 description: >
     Query foreign LLM for chat.
     Use this skill if a foreign LLM like OpenAI ChatGPT, Google Gemini,
@@ -15,17 +15,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Query Foreign LLM for Chat
-==========================
-
 <skill name="ase-meta-chat">
 Query Foreign LLM for Chat
 </skill>
 
-<role>
-Your role is to act as a proxy to query a foreign LLM for a single chat message.
-</role>
-
 <objective>
 Query foreign LLM for: <query>$ARGUMENTS</query>
 </objective>

package/plugin/skills/ase-meta-chat/help.md

@@ -0,0 +1,45 @@
+
+##  NAME
+
+`ase-meta-chat` - Query Foreign LLM for Chat
+
+##  SYNOPSIS
+
+`ase-meta-chat`
+    [`--help`|`-h`]
+    *llm* *query*
+
+##  DESCRIPTION
+
+The `ase-meta-chat` skill queries a *foreign LLM* (such as OpenAI
+ChatGPT, Google Gemini, DeepSeek, xAI Grok, Z.AI GLM, or Alibaba
+Qwen) with a single chat message. The underlying `ase:ase-meta-chat`
+sub-agent is invoked and its plain response is shown back verbatim
+without any further interpretation.
+
+##  ARGUMENTS
+
+*llm*:
+    Identifier of the foreign LLM to query, e.g. `chatgpt`,
+    `gemini`, `deepseek`, `grok`, `glm`, or `qwen`.
+
+*query*:
+    The chat message to send to the foreign LLM.
+
+##  EXAMPLES
+
+Ask ChatGPT a quick question:
+
+```text
+❯ /ase-meta-chat chatgpt What is the best way to handle UTF-8 BOMs in JSON?
+```
+
+Ask Gemini for a brief comparison:
+
+```text
+❯ /ase-meta-chat gemini Compare gRPC and REST in one paragraph.
+```
+
+##  SEE ALSO
+
+`ase-meta-quorum`, `ase-meta-search`.