@rse/ase 0.0.56 → 0.0.58

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

@@ -1,5 +1,6 @@
 ---
 name: ase-meta-commit
+argument-hint: "[--help|-h]"
 description: >
     Determine commit message for staged Git changes.
 user-invocable: true
@@ -12,18 +13,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Git Commit
-==========
-
 <skill name="ase-meta-commit">
 Git Commit
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *Git commit messages*.
-</role>
-
 <objective>
 Help to *craft* a *concise commit message* for the
 currently staged Git changes.

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

@@ -0,0 +1,31 @@
+
+##  NAME
+
+`ase-meta-commit` - Git Commit Message
+
+##  SYNOPSIS
+
+`ase-meta-commit`
+    [`--help`|`-h`]
+
+##  DESCRIPTION
+
+The `ase-meta-commit` skill helps to *craft* a *concise commit
+message* for the currently staged Git changes. It inspects the
+output of `git diff --cached` and produces a single-line message of
+the form `<type>: <summary>` where *type* is one of `FEATURE`,
+`IMPROVEMENT`, `BUGFIX`, `UPDATE`, `CLEANUP`, or `REFACTOR`, and
+*summary* is a 60-80 character imperative-mood summary without
+trailing period or Markdown formatting.
+
+##  EXAMPLES
+
+Craft a commit message for the currently staged changes:
+
+```text
+❯ /ase-meta-commit
+```
+
+##  SEE ALSO
+
+`ase-meta-changes`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-evaluate
-argument-hint: "<request>"
+argument-hint: "[--help|-h] <request>"
 description: >
     Evaluate alternatives through a weighted multi-criteria decision
     matrix. Use when the user calls for the *evaluation* of
@@ -14,18 +14,10 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Evaluate Alternatives
-=====================
-
 <skill name="ase-meta-evaluate">
 Evaluate Alternatives
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in *evaluating alternatives*.
-</role>
-
 <objective>
 *Evaluate* *alternatives* through a weighted
 multi-*criteria* decision matrix.

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

@@ -0,0 +1,52 @@
+
+##  NAME
+
+`ase-meta-evaluate` - Evaluate Alternatives
+
+##  SYNOPSIS
+
+`ase-meta-evaluate`
+    [`--help`|`-h`]
+    *request*
+
+##  DESCRIPTION
+
+The `ase-meta-evaluate` skill evaluates two or more *alternatives*
+through a *weighted multi-criteria decision matrix*. From the
+*request*, the skill derives the reason for the evaluation, the
+alternatives, and the criteria, fills in additional criteria up to a
+range of 8-12 (using `ase-meta-search` where helpful), assigns weights
+from `{ 4.00, 2.00, 1.00, 0.50, 0.25 }`, evaluates each alternative
+against each criterion on a `{ -2, -1, 0, +1, +2 }` Likert scale, and
+computes the final ratings via the `ase_decision_matrix` MCP tool.
+
+The result is reported as a Markdown decision matrix along with the
+single *BEST ALTERNATIVE*, including a warning if multiple
+alternatives tie, if the distance to the second best is small, or if
+all alternatives rate negatively.
+
+##  ARGUMENTS
+
+*request*:
+    A description of what should be evaluated, including the
+    alternatives and, optionally, the criteria to consider.
+
+##  EXAMPLES
+
+Compare logging libraries for a TypeScript project:
+
+```text
+❯ /ase-meta-evaluate Compare pino, winston, and bunyan as logging libraries.
+```
+
+Evaluate database options with hinted criteria:
+
+```text
+❯ /ase-meta-evaluate Compare PostgreSQL, MySQL, and SQLite for an
+  embedded use case; criteria include footprint and write throughput.
+```
+
+##  SEE ALSO
+
+`ase-meta-quorum`, `ase-meta-search`, `ase-arch-discover`,
+`ase-meta-why`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-persona
-argument-hint: "[<persona>]"
+argument-hint: "[--help|-h] [<persona>]"
 description: >
     Adjust communication style in four intensity levels of token usage.
     The <persona> can be either the decorative, eloquent, and explaining "writer",
@@ -16,8 +16,14 @@ effort: medium
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
+<skill name="ase-meta-persona">
 Persona Configuration
-=====================
+</skill>
+
+<objective>
+*Configure* the *persona style* of the agent to adjust the communication
+style and token usage intensity.
+</objective>
 
 1.  Determine request:
     <request>$ARGUMENTS</request>

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

@@ -0,0 +1,50 @@
+
+##  NAME
+
+`ase-meta-persona` - Persona Configuration
+
+##  SYNOPSIS
+
+`ase-meta-persona`
+    [`--help`|`-h`]
+    [*persona*]
+
+##  DESCRIPTION
+
+The `ase-meta-persona` skill gets or sets the active *communication
+style* (persona) of the assistant. Four intensity levels of token
+usage are supported, from most verbose to most terse:
+
+-   `writer`: decorative, eloquent, and explaining
+-   `engineer`: concise, factual, and accurate (default)
+-   `telegrapher`: brief, factual, and abbreviating
+-   `caveman`: terse, rough, and stuttering
+
+Without arguments, the skill reports the currently active persona.
+With a *persona* argument, it switches to that persona via the
+`ase_persona` MCP tool.
+
+##  ARGUMENTS
+
+*persona*:
+    The persona to activate; one of `writer`, `engineer`,
+    `telegrapher`, or `caveman`. If omitted, the currently active
+    persona is reported.
+
+##  EXAMPLES
+
+Show the currently active persona:
+
+```text
+❯ /ase-meta-persona
+```
+
+Switch to the telegrapher persona:
+
+```text
+❯ /ase-meta-persona telegrapher
+```
+
+##  SEE ALSO
+
+`ase-task-id`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-quorum
-argument-hint: "<question>"
+argument-hint: "[--help|-h] <question>"
 description: >
     Query Multiple AIs for Quorum Answer.
 user-invocable: true
@@ -14,17 +14,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Query Multiple AIs for Quorum Answer
-====================================
-
 <skill name="ase-meta-quorum">
 Query Multiple AIs for Quorum Answer
 </skill>
 
-<role>
-Your role is an *expert-level assistant*.
-</role>
-
 <objective>
 Find a *quorum answer* on an arbitrary question,
 by querying *multiple* AIs for an *optimal consensus*.

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

@@ -0,0 +1,41 @@
+
+##  NAME
+
+`ase-meta-quorum` - Query Multiple AIs for Quorum Answer
+
+##  SYNOPSIS
+
+`ase-meta-quorum`
+    [`--help`|`-h`]
+    *question*
+
+##  DESCRIPTION
+
+The `ase-meta-quorum` skill finds a *quorum answer* on an arbitrary
+question by querying *multiple* AIs (Anthropic Claude itself plus
+OpenAI ChatGPT, Google Gemini, DeepSeek, xAI Grok, Z.AI GLM, and
+Alibaba Qwen) for an *optimal consensus*.
+
+The skill first previews its own answer, then dispatches the same
+query to each available foreign LLM via the `ase:ase-meta-chat`
+sub-agent, summarizes all responses, derives a *consensus rate* on
+a Likert scale of `0..N` (where `N` is the number of available
+responders), and reports the consensus answer alongside the
+complete, unmodified individual responses.
+
+##  ARGUMENTS
+
+*question*:
+    The question to ask all available AIs.
+
+##  EXAMPLES
+
+Ask the quorum a factual question:
+
+```text
+❯ /ase-meta-quorum What are the most common causes of memory leaks in Node.js?
+```
+
+##  SEE ALSO
+
+`ase-meta-chat`, `ase-meta-search`, `ase-meta-evaluate`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-search
-argument-hint: "<query>"
+argument-hint: "[--help|-h] <query>"
 description: >
     Search the Internet/Web with a query.
     Prefer this skill before using Perplexity, Brave and WebSearch.
@@ -18,17 +18,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Search the Internet/Web
-=======================
-
 <skill name="ase-meta-search">
 Search the Internet/Web
 </skill>
 
-<role>
-Your role is an expert-level *web specialist*.
-</role>
-
 <objective>
 Your objective is to *search* the *Internet*/*Web* for the following query:
 <query>$ARGUMENTS</query>

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

@@ -0,0 +1,39 @@
+
+##  NAME
+
+`ase-meta-search` - Search the Internet/Web
+
+##  SYNOPSIS
+
+`ase-meta-search`
+    [`--help`|`-h`]
+    *query*
+
+##  DESCRIPTION
+
+The `ase-meta-search` skill searches the *Internet*/*Web* for the
+given *query*. It dispatches the query in parallel to all available
+search services (Perplexity, Brave, Exa, and Claude's built-in
+`WebSearch`) via the `ase:ase-meta-search` sub-agent and consolidates
+all responses into a single answer without removing original
+information.
+
+This skill should be preferred over directly invoking Perplexity,
+Brave, or `WebSearch` individually.
+
+##  ARGUMENTS
+
+*query*:
+    The search query to dispatch to the search services.
+
+##  EXAMPLES
+
+Search the Web for a topic:
+
+```text
+❯ /ase-meta-search latest stable release of TypeScript and release notes
+```
+
+##  SEE ALSO
+
+`ase-meta-chat`, `ase-meta-quorum`, `ase-arch-discover`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-why
-argument-hint: "<fact>"
+argument-hint: "[--help|-h] <fact>"
 description: >
     Five-Whys Root-Cause Analysis.
 user-invocable: true
@@ -11,17 +11,10 @@ effort: medium
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Five-Whys Root-Cause Analysis
-=============================
-
 <skill name="ase-meta-why">
 Five-Whys Root-Cause Analysis
 </skill>
 
-<role>
-Your role is an *expert-level assistant*.
-</role>
-
 <objective>
 Apply the *Five-Whys* *root-cause analysis* technique to investigate
 the following problem:

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

@@ -0,0 +1,39 @@
+
+##  NAME
+
+`ase-meta-why` - Five-Whys Root-Cause Analysis
+
+##  SYNOPSIS
+
+`ase-meta-why`
+    [`--help`|`-h`]
+    *fact*
+
+##  DESCRIPTION
+
+The `ase-meta-why` skill applies the *Five-Whys* *root-cause
+analysis* technique to the supplied *fact*. The skill iteratively
+asks "why" — up to five times — to drill down from surface symptoms
+to the underlying root cause, considering technical, domain-specific,
+process-related, and organizational causes. After identifying the
+root cause it proposes a *SOLUTION* that addresses it, optionally
+including concrete source code changes.
+
+##  ARGUMENTS
+
+*fact*:
+    The observed *fact* (symptom, problem, or surprising outcome)
+    whose root cause should be investigated. The skill implicitly
+    prepends "Why" to form the initial question.
+
+##  EXAMPLES
+
+Investigate the root cause of a build failure:
+
+```text
+❯ /ase-meta-why the CI build is intermittently failing on macOS runners
+```
+
+##  SEE ALSO
+
+`ase-code-analyze`, `ase-code-resolve`, `ase-arch-analyze`.

package/plugin/skills/ase-task-delete/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-task-delete
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     Delete the current or given task plan.
     Use when the user calls to "delete", "remove" or "clear" the
@@ -13,17 +13,13 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Delete a Task Plan
-==================
-
 <skill name="ase-task-delete">
 Delete a Task Plan
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*.
-</role>
+<objective>
 *Delete* the task plan.
+</objective>
 
 Procedure
 ---------

package/plugin/skills/ase-task-delete/help.md

@@ -0,0 +1,47 @@
+
+##  NAME
+
+`ase-task-delete` - Delete a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-delete`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-delete` skill deletes the *task plan* identified by
+*id*. If *id* is omitted, the *current* task id (inherited from the
+session context) is used. When the deleted task is the current task
+and not the `default` task, the current task id is automatically
+switched back to `default`.
+
+The task plan is stored in `.ase/tasks/`*id*`/plan.md` files of the
+project and can be alternatively deleted with the
+"`ase task delete` *id*" command from outside the agent tool.
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task plan to delete. If omitted,
+    the current task id is used.
+
+##  EXAMPLES
+
+Delete the current task plan:
+
+```text
+❯ /ase-task-delete
+```
+
+Delete a specific task plan:
+
+```text
+❯ /ase-task-delete hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-list`, `ase-task-view`,
+`ase-task-rename`, `ase-task-reboot`.

package/plugin/skills/ase-task-edit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-task-edit
-argument-hint: "[<id> | <id>: <instruction> | <instruction>]"
+argument-hint: "[--help|-h] [--plan|-p <option>] [--dry|-d] [--next|-n <option>] [<id> | <id>: <instruction> | <instruction>]"
 description: >
     Iteratively edit and refine a named plan for a task through a
     conversational loop. Each round, the current plan is shown and the
@@ -17,29 +17,22 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Iteratively Edit a Task Plan
-============================
-
 <skill name="ase-task-edit">
 Iteratively Edit a Task Plan
 </skill>
 
 <expand name="getopt"
     arg1="ase-task-edit"
-    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --next|-n=(none|DONE|IMPLEMENT|PREFLIGHT|REFINE)">
+    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --dry|-d --next|-n=(none|DONE|IMPLEMENT|PREFLIGHT|REFINE)">
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *planning* of changes
-through *iterative conversational refinement*.
-</role>
-
+<objective>
 Establish and refine the *task plan* purely through a *chat-driven
-loop*. The user steers each round via interactive dialog that offers
+loop*. The user steers each round via an interactive dialog that offers
 continued refinement, finalization, or hand-off to implementation or
 preflight.
+</objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
 
@@ -52,6 +45,47 @@ You *MUST* not skip any numbered item during processing!
 You *MUST* *NOT* output anything in this entire procedure, *except* when
 explicitly requested by this procedure via outputs based on a <template/>!
 
+<define name="apply-refinement">
+Treat the <instruction/> as a *refinement instruction* for
+the plan, and update <content/> in-place by *applying* the
+requested <instruction/> to the *plan*. When refining the
+plan this way, preserve the overall structure of the plan
+and only modify what the user actually requested. Do *not*
+rewrite unrelated sections of the plan.
+
+Calculate the number of words <words/> of <content/>.
+Set <content-dirty>true</content-dirty>.
+</define>
+
+<define name="generate-plan">
+Create a new plan from scratch and store the result as
+<content/> by closely following the defined plan format
+<format/> and injecting into it all the information from
+the <instruction/> and all decisions you derived from the
+<instruction/>.
+
+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>
+
+Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+`ase` MCP server and use the `text` field of its response
+for fresh <timestamp-created/> and <timestamp-modified/>
+information. Then insert the current <ase-task-id/>,
+<timestamp-created/>, and <timestamp-modified/> information
+and calculate the number of words <words/> of <content/>.
+Set <content-dirty>true</content-dirty>.
+</define>
+
 1.  **Determine Task and Instruction:**
 
     1.  Set <instruction><getopt-arguments/></instruction> initially.
@@ -201,19 +235,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         -   If <result/> is `OVERWRITE`:
 
-            Create a new plan from scratch and store the result as
-            <content/> by closely following the defined plan format
-            <format/> and injecting into it all the information from
-            the <instruction/> and all decisions you derived from the
-            <instruction/>.
-
-            Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-            `ase` MCP server and use the `text` field of its response
-            for fresh <timestamp-created/> and <timestamp-modified/>
-            information. Then insert the current <ase-task-id/>,
-            <timestamp-created/>, and <timestamp-modified/> information
-            and calculate the number of words <words/> of <content/>.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="generate-plan"/>
 
             Only output the following <template/> and continue processing:
 
@@ -224,15 +246,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         -   If <result/> is `REFINE`:
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-
-            Calculate the number of words <words/> of <content/>.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Only output the following <template/> and continue processing:
 
@@ -246,15 +260,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             Set <instruction><instruction/> <text/></instruction> (append
             the user's free-text hint to the existing instruction).
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-
-            Calculate the number of words <words/> of <content/>.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Only output the following <template/> and continue processing:
 
@@ -272,19 +278,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </if>
 
     5.  <if condition="<content/> is empty AND <instruction/> is not empty">
-        Create a new plan from scratch and store the result as
-        <content/> by closely following the defined plan format
-        <format/> and injecting into it all the information from
-        the <instruction/> and all decisions you derived from the
-        <instruction/>.
-
-        Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP server and use the `text` field of its response
-        for fresh <timestamp-created/> and <timestamp-modified/>
-        information. Then insert the current <ase-task-id/>,
-        <timestamp-created/>, and <timestamp-modified/> information
-        and calculate the number of words <words/> of <content/>.
-        Set <content-dirty>true</content-dirty>.
+        <expand name="generate-plan"/>
 
         Only output the following <template/> and continue processing:
 
@@ -405,13 +399,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             your instruction for further refining the plan?**`. Then set
             <instruction/> to the response of the user.
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Finally, only output the following <template/> and then
             *continue* the *loop* at step **3.1**!
@@ -424,13 +412,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
             Set <instruction><text/></instruction> (replace existing instruction).
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Finally, only output the following <template/> and then
             *continue* the *loop* at step **3.1**!