@rse/ase 0.0.46 → 0.0.49

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

@@ -3,14 +3,16 @@ name: ase-docs-proofread
 argument-hint: "<docs-reference>"
 description: >
     Analyze the documents for spelling, punctuation, or grammar errors.
-    Use when the user wants to "spellcheck", "proofread", or "lint" a text or document.
+    Use when the user wants to "proofread" or "spellcheck" a document.
 user-invocable: true
 disable-model-invocation: false
-effort: high
+effort: medium
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 Proofread Documentation
 =======================
@@ -19,6 +21,12 @@ Proofread Documentation
 Analyze the documents for spelling, punctuation, or grammar errors.
 </skill>
 
+<expand name="getopt"
+    arg1="ase-docs-proofread"
+    arg2="--auto|-a">
+    $ARGUMENTS
+</expand>
+
 <role>
 Your role is an experienced, *expert-level proofreader*, specialized in
 checking and correcting the *spelling*, *punctuation* and *grammar* of
@@ -26,93 +34,185 @@ documents.
 </role>
 
 <objective>
-*Analyze* the documents of $ARGUMENTS for problems in their *spelling*,
-*punctuation* or *grammar* and immediately correct all found problems.
+*Analyze* the documents of `<getopt-arguments/>` for problems in their
+*spelling*, *punctuation*, or *grammar* and propose corrections.
 </objective>
 
 <flow>
 
-1.  <step id="STEP 1: Investigation & Checking">
-    Investigate on the document base by using the `Read` tool to read all
-    referenced document files. For all contained texts in those files,
-    check the following problem types *ONLY*:
+1.  <step id="STEP 1: Investigation">
+
+    First, use the following <template/> to give a hint on this step:
+
+    <template>
+    &#x26AA; **PROOFREADING INVESTIGATION**
+    </template>
+
+    Dispatch the investigation to a *sub-agent* via the `Agent`
+    tool so that *no* investigation details leak into the user-visible
+    transcript. The sub-agent performs the silent reading and checking;
+    only its final structured return value is consumed here.
+
+    For this, invoke *exactly once* the tool:
 
-    - **Spelling**
-    - **Punctuation**
-    - **Grammar**
+    ```text
+        Agent(
+            name:          "ase-docs-proofread",
+            description:   "Proofread Investigation",
+            subagent_type: "ase-docs-proofread",
+            mode:          "plan",
+            prompt:        <getopt-arguments/>
+        )
+    ```
 
-    You *MUST* collect *all* found problems into an internal list only,
-    and then set <problems/> to the value of this list.
+    Parse the single result message of the `Agent` tool as a JSON array
+    and set <problems/> to that list.
 
-    You *MUST* *NOT* propose document changes in this step 1.
-    You *MUST* *NOT* output anything in this step 1.
+    You *MUST* *NOT* output anything at all in this step 1 beyond the
+    single `Agent` tool invocation.
     </step>
 
 2.  <step id="STEP 2: Summary">
+
     Use the following <template/> to give a summary of the detected
     problems in <problems/>:
 
     <template>
+    &#x26AA; **PROOFREADING SUMMARY**:
+
     | *Proofread Type* | *Proofread Result*      |
     | ---------------- | ----------------------- |
     | **SPELLING**:    | **<n/>** problems found |
     | **PUNCTUATION**: | **<m/>** problems found |
     | **GRAMMAR**:     | **<k/>** problems found |
+
     </template>
 
     Hints:
 
-    -   <n/> is the number of spelling problems in <problems/>
-    -   <m/> is the number of punctuation problems in <problems/>
-    -   <k/> is the number of grammar problems in <problems/>
+    -   <n/> is the number of problems with `type` equal to `SPELLING`    in <problems/>
+    -   <m/> is the number of problems with `type` equal to `PUNCTUATION` in <problems/>
+    -   <k/> is the number of problems with `type` equal to `GRAMMAR`     in <problems/>
+
     </step>
 
-3.  <step id="STEP 3: Details & Correction">
+3.  <step id="STEP 3: Correction">
 
-    <for items="<problems/>">
+    1.  You *MUST* call the MCP tool `config_set(key: "agent.skill", val:
+        "ase-docs-proofread", scope: "session:<ase-session-id/>")` of the
+        `ase` MCP server.
 
-    For the current <item/> from the collected list <problems/>, do the
-    following:
+    2.  Iterate over all problems:
 
-    1.  Report the problem with the following <template/>:
+        <for items="<problems/>">
 
-        <template>
-        &#x1F7E0; **<type/>**: [`<file/>`:<line/>]: <description/>
-        </template>
+        1.  Set <type/>           to the `type` field of <item/>.
+            Set <file/>           to the `file` field of <item/>.
+            Set <line/>           to the `line` field of <item/>.
+            Set <description/>    to the `description` field of <item/>.
+            Set <context-before/> to the `context_before` field of <item/>.
+            Set <old-text/>       to the `old_text` field of <item/>.
+            Set <new-text/>       to the `new_text` field of <item/>.
+            Set <context-after/>  to the `context_after` field of <item/>.
+
+        2.  Report the problem with the following <template/>:
+
+            <template>
+            &#x1F7E0; **<type/> PROBLEM**: `<file/>`:<line/>:
+
+            <description/>
+            </template>
+
+        3.  <if condition="<getopt-option-auto/> is not 'true'">
+
+            Render the proposed correction as a *unified diff* with *one*
+            line of context in a fenced block based on the following <template/>:
+
+            <template>
+
+            &#x1F535; **<type/> CORRECTION**:
 
-        Hints:
+            ```diff
+            --- <file/> (original)
+            +++ <file/> (corrected)
+            @@ -<line/>,<n/> +<line/>,<m/> @@
+             <context-before/>
+            -<old-text/>
+            +<new-text/>
+             <context-after/>
+            ```
 
-        -   The <type/> is `SPELLING`, `PUNCTUATION` or `GRAMMAR`
-            of <item/>.
+            </template>
 
-        -   The <file/> is the name of the document artifact of <item/>.
-            The <line/> is the line number of the document artifact of <item/>.
+            Hints:
+            -   The <n/> is the number of lines in <old-text/>.
+            -   The <m/> is the number of lines in <new-text/>.
 
-        -   The <description/> is an ultra brief and concise description
-            of the problem <item/> with a hint what is wrong and why
-            it is wrong. In <description/>, markup all verbatim words
-            <words/> related to the checked text (or the proposed
-            corrected text) as quoted strings containing monospaced text
-            with the Markdown <template>"`<words/>`"</template>.
+            </if>
 
-    2.  Propose a direct change to the corresponding document via the
-        interactive `Edit` tool.
+        4.  <if condition="<getopt-option-auto/> is not 'true'">
 
-        **IMPORTANT**: Regardless of whether the change was *accepted*
-        or *rejected* by the user (i.e., even if the `Edit` tool returns
-        an error like "The user doesn't want to proceed with this tool
-        use" or "User rejected"), you *MUST* immediately *CONTINUE* with
-        the *next* <item/> in the iteration.
+            Ask the user how to proceed via an interactive user dialog:
 
-        Do *NOT* stop. Do *NOT* ask the user for confirmation. Do *NOT*
-        summarize. A rejection is *NOT* a signal to abort; it is only
-        a signal that *this one* change is skipped. Only after *all*
-        problems have been processed may you stop.
+            <expand name="user-dialog">
+                CORRECTION: How would you like to proceed with this proposed correction?
+                ACCEPT: Apply the proposed correction.
+                REJECT: Skip this proposed correction.
+            </expand>
 
-    </for>
+            </if>
+
+            <if condition="<getopt-option-auto/> is 'true'">
+
+            Set <result>ACCEPT</result>.
+
+            </if>
+
+        5.  Check <result/> and dispatch accordingly:
+
+            -   <if condition="<result/> is 'ACCEPT'">
+
+                Invoke the `Edit` tool to apply the change exactly as shown
+                in the diff. The operation will be auto-approved because of
+                the active proofread marker, so *no* interactive permission
+                prompt will appear. Then continue with the next <item/>.
+
+                </if>
+
+            -   <if condition="<result/> starts with 'OTHER'">
+
+                Generate a *new* proposal for the *same* <item/>,
+                incorporating the user's free-text hint from <result/>
+                after the "OTHER:" prefix, and loop back to substep 2 of
+                this iteration. There is *no* cap on refinement rounds —
+                keep refining until the user picks `ACCEPT` or `REJECT`.
+
+                </if>
+
+            -   <if condition="
+                    <result/> is 'REJECT' or
+                    <result/> is 'CANCEL' or
+                    <result/> starts with 'ERROR'
+                ">
+
+                Skip this <item/> without any `Edit` call and continue
+                with the next <item/>.
+
+                </if>
+
+        </for>
+
+    3.  You *MUST* call the MCP tool `config_delete(key: "agent.skill",
+        scope: "session:<ase-session-id/>")` of the `ase` MCP server.
+
+    4.  You *MUST* *NOT* output any further additional explanations or
+        summaries at the end of this skill processing, except for the
+        following final <template/>:
+
+        <template>
+        &#x26AA; **PROOFREAD FINISHED**
+        </template>
 
-    You *MUST* *NOT* output any further additional explanations or
-    summaries at the end of this skill processing.
     </step>
 
 </flow>

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

@@ -66,7 +66,7 @@ are also grouped and sorted according to the above <prefix/>es.
    </step>
 
 3. <step id="STEP 3: Complete ChangeLog entries">
-   Without immediately modifying `CHANGELOG.md` file,
+   Without immediately modifying the `CHANGELOG.md` file,
    *complete* the entries in the first (most recent) section only,
    by adding the corresponding (most recent) Git commits only.
    For each Git commit, reduce the Git commit messages to a single
@@ -74,17 +74,17 @@ are also grouped and sorted according to the above <prefix/>es.
    </step>
 
 4. <step id="STEP 4: Consolidate ChangeLog entries">
-   Without immediately modifying `CHANGELOG.md` file,
+   Without immediately modifying the `CHANGELOG.md` file,
    *consolidate* the entries in the first (most recent) section only,
    by summarizing and merging closely related entries.
    Perform the entry consolidation per prefix group only.
-   If a changelog <summary/> is too short or is too little comprehensible
+   If a changelog <summary/> is too short or is not comprehensible enough
    because of too little context, add some context, especially references
    to the class/module/package, etc.
    </step>
 
 5. <step id="STEP 5: Sort ChangeLog entries">
-   Without immediately modifying `CHANGELOG.md` file,
+   Without immediately modifying the `CHANGELOG.md` file,
    *sort* the entries in the first (most recent) section only.
    Instead of the chronological commit order, group the entries
    by the prefixes.

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

@@ -5,9 +5,9 @@ description: >
     *Always use* when you have to *visualize*
     structure/layout/components/dependencies as Flowchart,
     control-flow/branching/concurrency as Flowchart,
-    state-machine/states/transitions as an UML State Diagram,
-    data-flow/actors/messages/protocols as an UML Sequence Diagram,
-    data-structure/classes/methods as an UML Class Diagram,
+    state-machine/states/transitions as a UML State Diagram,
+    data-flow/actors/messages/protocols as a UML Sequence Diagram,
+    data-structure/classes/methods as a UML Class Diagram,
     data-model/entities/relationships as an ER Diagram, or
     metrics/distributions/time-series as XY-Charts.
 user-invocable: false
@@ -71,7 +71,7 @@ Rules
     In other words, after the `diagram` tool call completes, the
     skill *MUST* copy the tool's `text` result *verbatim* into a
     Markdown-fenced code block (triple backticks), directly placed
-    in the response text immediately after the MCP tool call -— the
+    in the response text immediately after the MCP tool call — the
     user reads the Markdown fenced block in the response, not the
     (truncated) tool call display. Emitting only the tool call without
     the reproduction of the `text` output is a defect: the diagram is
@@ -95,7 +95,7 @@ Rules
     For *comparison diagrams* (e.g., *current vs. proposed*, *before
     vs. after*), render each side as a *separate* Mermaid diagram
     specification via the `diagram` tool from the `ase` MCP service, and
-    then stack the two rendered blocks *vertically* -— each preceded by
+    then stack the two rendered blocks *vertically* — each preceded by
     a bold label (`**BEFORE:**` / `**AFTER:**`, or similar). Do *not*
     attempt side-by-side layout.
 

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

@@ -121,7 +121,7 @@ multi-*criteria* decision matrix.
         important, over normal, to less important). Do not output anything.
 
     -   Ensure the final number of criteria is always within the range of
-        minimum 8 and maximum 12: if less than 8 criteria were requested,
+        minimum 8 and maximum 12: if fewer than 8 criteria were requested,
         use the set of alternatives to decide on additional criteria
         which potentially allow best to triage the alternatives, take the
         <reason/> into account, and use the `ase-meta-search` skill (drawing from
@@ -248,7 +248,7 @@ multi-*criteria* decision matrix.
         ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
         </template>
 
-    -   Otherwise (<percentage/> is greater than or equal 0.10), output
+    -   Otherwise (<percentage/> is greater than or equal to 0.10), output
         just the following <template/> and do not output anything else:
 
         <template>

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

@@ -6,7 +6,7 @@ description: >
     The <persona> can be either the decorative, eloquent, and explaining "writer",
     the concise, factual, and accurate "engineer" (default),
     the brief, factual, and abbreviating "telegrapher",
-    the terse, rough and stuttering "caveman".
+    the terse, rough, and stuttering "caveman".
     Use when user says "persona <persona>" or "be <persona>".
 user-invocable: true
 disable-model-invocation: false

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

@@ -81,7 +81,7 @@ by querying *multiple* AIs for an *optimal consensus*.
     If all responses disagree, the consensus <c/> is zero.
     If all responses agree, <c/> is <n/>.
 
-    If not all AIs agree, determine a <disagreement/> information,
+    If not all AIs agree, determine <disagreement/> information,
     formatted as `(disagreement: <ai/>, <ai/>, [...])` where <ai/> is a
     name of an AI which disagreed with the consensus. Else, if all AIs
     agree, set <disagreement></disagreement>.

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

@@ -0,0 +1,92 @@
+---
+name: ase-task-rename
+argument-hint: "[<old>] <new>"
+description: >
+    Rename the current or given task plan.
+    Use when the user calls to "rename", "move" or "relabel" the
+    "task", "plan", "spec", or "specification".
+user-invocable: true
+disable-model-invocation: false
+effort: low
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+
+Rename a Task Plan
+==================
+
+<skill name="ase-task-rename">
+Rename a Task Plan
+</skill>
+
+Your role is an experienced, *expert-level assistant*.
+*Rename* the task plan.
+
+Procedure
+---------
+
+You *MUST* follow the following numbered items *strictly* *sequentially*!
+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/>!
+
+1.  **Determine Task:**
+
+    1.  Parse <arguments>$ARGUMENTS</arguments> into a whitespace-separated
+        list of tokens. Inherit the always existing <ase-task-id/> from
+        the current context. Do not output anything.
+
+    2.  <if condition="<arguments/> contains two tokens">
+        Set <old/> to the first token of <arguments/>.
+        Set <new/> to the second token of <arguments/>.
+        Do not output anything.
+        </if>
+
+    3.  <if condition="<arguments/> contains exactly one token">
+        Set <old><ase-task-id/></old>.
+        Set <new/> to the single token of <arguments/>.
+        Do not output anything.
+        </if>
+
+    4.  <if condition="<arguments/> is empty OR contains more than two tokens">
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ☻ skill: **ase-task-rename**, ▶ ERROR: expected `[<old>] <new>` arguments
+        </template>
+        </if>
+
+2.  **Perform Operation**:
+
+    1.  Call the `task_rename(old: <old/>, new: <new/>)` tool of the
+        `ase` MCP service to rename the task plan and set <text/> to the
+        `text` output field of this `task_rename` tool call. Do not
+        output anything related to this MCP tool call.
+
+        -   If <text/> starts with `ERROR:` or `WARNING:`:
+            Only output the following <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<old/>**, ▶ status: **<text/>**
+            </template>
+
+        -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
+            Only output the following <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<new/>**, ▶ status: **task renamed**
+            </template>
+
+    2.  <if condition="<old/> is equal <ase-task-id/>">
+        Set <ase-task-id><new/></ase-task-id>. Call the `task_id(id:
+        <ase-task-id/>, session: <ase-session-id/>)` tool from the `ase`
+        MCP service to switch the task to the renamed task. Only output
+        the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task switched**
+        </template>
+        </if>