@rse/ase 0.9.6 → 0.9.8

package/plugin/meta/ase-skill.md

@@ -25,6 +25,18 @@ Skill Output
     Unicode characters, and the potential reduction of prose according
     to the currently defined persona style.
 
+-   *IMPORTANT*: For *Final-Message-Only Display* ("focus mode"):
+    some agent harnesses show the user only the *final* text message of
+    a turn and *hide* all text emitted *between* tool calls. If your
+    harness instructions indicate such a mode (e.g. *Claude Code* with
+    "focus mode" enabled), you *MUST* repeat *all* <template/> outputs
+    emitted since the last shown final text message -- *verbatim*, in
+    their *original order*, and each only *once* -- at the *top* of the
+    next final text message (i.e. the text after the last tool call of
+    a turn). Never *drop* or *summarize* a <template/> output just
+    because it would land between tool calls. If no such display mode
+    is indicated, do *not* repeat anything.
+
 -   *IMPORTANT*: The active *persona style* (see `ase-persona.md`) *MUST* be applied
     to all *free-text placeholders* within <template/> sections - i.e. any placeholder
     whose content you author yourself (such as `<description/>`, `<title/>`, `<objective/>`,
@@ -98,14 +110,21 @@ Skill Sequential Processing
 -   *IMPORTANT*: For each given <flow/>, you *MUST* use the
     `TaskCreate` tool to create a corresponding set of processing steps.
 
-    Each `<step id="xxx" [...]/>` corresponds to a `TaskCreate({
-    subject: "xxx", description: "xxx", activeForm: "xxx" })`. In other
-    words, use the text of the `id` attribute of <step/> for both
-    the `subject`, the `description`, and the `activeForm` fields of
+    Each `<step id="xxx" [...]>...</step>` corresponds to a
+    `TaskCreate({ subject: "xxx", description: "xxx" })`. In other
+    words, use the text of the `id` attribute of <step/> exactly
+    *as-is* for both the `subject`, and the `description` fields of
     `TaskCreate`.
 
-    Make the `TaskCreate` tool calls *sequentially*, *not* in parallel,
-    so the user can see intermediate results.
+    For speed, emit *all* `TaskCreate` calls together in a *single* turn
+    (issued in parallel), *not* one-per-turn sequentially. Do *not*
+    rely on the call order to establish the step order, as the parallel
+    results carry no guaranteed ordering. Instead, in the *immediately
+    following* turn, establish the strict order explicitly by chaining
+    the created tasks with `TaskUpdate`: for each <step/> after the
+    first one, call `TaskUpdate({ taskId: "<this/>", addBlockedBy:
+    [ "<prev/>" ] })` so that every step (with `taskId` <this/>) is
+    blocked by its predecessor step (with `taskId` <prev/>).
 
 -   *IMPORTANT*: For each <step/> you *MUST* use the `TaskUpdate` tool
     for updating its status during processing.
@@ -208,7 +227,7 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-head title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 8 - length("<title/>")), i.e., <bar/> is
+    (where <bar/> = "─" x (70 - 16 - length("<title/>")), i.e., <bar/> is
     the "─" character repeated (70 - 16 - length("<title/>")) times):
 
     <template>
@@ -226,8 +245,8 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-foot title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 8 - length("<title/>")), i.e., <bar/> is
-    the "─" character repeated (70 - 16 - length("<title/>")) times):
+    (where <bar/> = "─" x (70 - 16 - length("<title/>")), i.e., <bar/> is
+    the "─" character repeated (71 - 16 - length("<title/>")) times):
 
     <template>
 

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.6",
+    "version":                              "0.9.8",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -15,11 +15,11 @@
     },
     "devDependencies": {
         "@rse/stx":                         "1.1.5",
-        "markdownlint":                     "0.40.0",
+        "markdownlint":                     "0.41.0",
         "markdownlint-cli2":                "0.22.1",
         "eslint":                           "10.4.1",
         "@eslint/markdown":                 "8.0.2",
-        "eslint-markdown":                  "0.10.0"
+        "eslint-markdown":                  "0.11.0"
     },
     "engines": {
         "npm":                              ">=10.0.0",

package/plugin/skills/ase-arch-analyze/SKILL.md

@@ -7,94 +7,94 @@ disable-model-invocation: false
 model: opus
 effort: high
 allowed-tools:
-    - "Bash(wc:*)"
-    - "Bash(ls:*)"
-    - "Bash(tree:*)"
-    - "Bash(file:*)"
-    - "Bash(du:*)"
-    - "Bash(stat:*)"
-    - "Bash(grep:*)"
-    - "Bash(awk:*)"
-    - "Bash(head:*)"
-    - "Bash(tail:*)"
-    - "Bash(sort:*)"
-    - "Bash(uniq:*)"
-    - "Bash(cat:*)"
-    - "Bash(cut:*)"
-    - "Bash(tr:*)"
-    - "Bash(nl:*)"
-    - "Bash(column:*)"
-    - "Bash(diff:*)"
-    - "Bash(cmp:*)"
-    - "Bash(jq:*)"
-    - "Bash(cloc:*)"
-    - "Bash(tokei:*)"
-    - "Bash(scc:*)"
-    - "Bash(basename:*)"
-    - "Bash(dirname:*)"
-    - "Bash(realpath:*)"
-    - "Bash(readlink:*)"
-    - "Bash(pwd:*)"
-    - "Bash(which:*)"
-    - "Bash(whereis:*)"
-    - "Bash(type:*)"
-    - "Bash(namei:*)"
-    - "Bash(git log:*)"
-    - "Bash(git show:*)"
-    - "Bash(git diff:*)"
-    - "Bash(git blame:*)"
-    - "Bash(git ls-files:*)"
-    - "Bash(git ls-tree:*)"
-    - "Bash(git grep:*)"
-    - "Bash(git status:*)"
-    - "Bash(git rev-list:*)"
-    - "Bash(git rev-parse:*)"
-    - "Bash(git for-each-ref:*)"
-    - "Bash(git reflog:*)"
-    - "Bash(git cat-file:*)"
-    - "Bash(git config --get:*)"
-    - "Bash(git config --list:*)"
-    - "Bash(git remote:*)"
-    - "Bash(git branch:*)"
-    - "Bash(git tag --list:*)"
-    - "Bash(git describe:*)"
-    - "Bash(git shortlog:*)"
-    - "Bash(find * -name:*)"
-    - "Bash(find * -type:*)"
-    - "Bash(find * -path:*)"
-    - "Bash(find * -maxdepth:*)"
-    - "Bash(find * -mindepth:*)"
-    - "Bash(find * -size:*)"
-    - "Bash(find * -mtime:*)"
-    - "Bash(find * -newer:*)"
-    - "Bash(git diff:* | awk:*)"
-    - "Bash(git diff:* | grep:*)"
-    - "Bash(git diff:* | head:*)"
-    - "Bash(git diff:* | tail:*)"
-    - "Bash(git diff:* | wc:*)"
-    - "Bash(git log:* | head:*)"
-    - "Bash(git log:* | grep:*)"
-    - "Bash(git log:* | wc:*)"
-    - "Bash(git show:* | head:*)"
-    - "Bash(git show:* | grep:*)"
-    - "Bash(git grep:* | head:*)"
-    - "Bash(git grep:* | wc:*)"
-    - "Bash(git ls-files:* | grep:*)"
-    - "Bash(git ls-files:* | head:*)"
-    - "Bash(git ls-files:* | wc:*)"
-    - "Bash(grep:* | head:*)"
-    - "Bash(grep:* | sort:*)"
-    - "Bash(grep:* | wc:*)"
-    - "Bash(grep:* | sort:* | uniq:*)"
-    - "Bash(cat:* | grep:*)"
-    - "Bash(cat:* | awk:*)"
-    - "Bash(cat:* | head:*)"
-    - "Bash(cat:* | wc:*)"
-    - "Bash(find:* | head:*)"
-    - "Bash(find:* | wc:*)"
-    - "Bash(awk:* | head:*)"
-    - "Bash(sort:* | uniq:*)"
-    - "Bash(sort:* | head:*)"
+    - "Bash(wc *)"
+    - "Bash(ls *)"
+    - "Bash(tree *)"
+    - "Bash(file *)"
+    - "Bash(du *)"
+    - "Bash(stat *)"
+    - "Bash(grep *)"
+    - "Bash(awk *)"
+    - "Bash(head *)"
+    - "Bash(tail *)"
+    - "Bash(sort *)"
+    - "Bash(uniq *)"
+    - "Bash(cat *)"
+    - "Bash(cut *)"
+    - "Bash(tr *)"
+    - "Bash(nl *)"
+    - "Bash(column *)"
+    - "Bash(diff *)"
+    - "Bash(cmp *)"
+    - "Bash(jq *)"
+    - "Bash(cloc *)"
+    - "Bash(tokei *)"
+    - "Bash(scc *)"
+    - "Bash(basename *)"
+    - "Bash(dirname *)"
+    - "Bash(realpath *)"
+    - "Bash(readlink *)"
+    - "Bash(pwd *)"
+    - "Bash(which *)"
+    - "Bash(whereis *)"
+    - "Bash(type *)"
+    - "Bash(namei *)"
+    - "Bash(git log *)"
+    - "Bash(git show *)"
+    - "Bash(git diff *)"
+    - "Bash(git blame *)"
+    - "Bash(git ls-files *)"
+    - "Bash(git ls-tree *)"
+    - "Bash(git grep *)"
+    - "Bash(git status *)"
+    - "Bash(git rev-list *)"
+    - "Bash(git rev-parse *)"
+    - "Bash(git for-each-ref *)"
+    - "Bash(git reflog *)"
+    - "Bash(git cat-file *)"
+    - "Bash(git config --get *)"
+    - "Bash(git config --list *)"
+    - "Bash(git remote *)"
+    - "Bash(git branch *)"
+    - "Bash(git tag --list *)"
+    - "Bash(git describe *)"
+    - "Bash(git shortlog *)"
+    - "Bash(find * -name *)"
+    - "Bash(find * -type *)"
+    - "Bash(find * -path *)"
+    - "Bash(find * -maxdepth *)"
+    - "Bash(find * -mindepth *)"
+    - "Bash(find * -size *)"
+    - "Bash(find * -mtime *)"
+    - "Bash(find * -newer *)"
+    - "Bash(git diff * | awk *)"
+    - "Bash(git diff * | grep *)"
+    - "Bash(git diff * | head *)"
+    - "Bash(git diff * | tail *)"
+    - "Bash(git diff * | wc *)"
+    - "Bash(git log * | head *)"
+    - "Bash(git log * | grep *)"
+    - "Bash(git log * | wc *)"
+    - "Bash(git show * | head *)"
+    - "Bash(git show * | grep *)"
+    - "Bash(git grep * | head *)"
+    - "Bash(git grep * | wc *)"
+    - "Bash(git ls-files * | grep *)"
+    - "Bash(git ls-files * | head *)"
+    - "Bash(git ls-files * | wc *)"
+    - "Bash(grep * | head *)"
+    - "Bash(grep * | sort *)"
+    - "Bash(grep * | wc *)"
+    - "Bash(grep * | sort * | uniq *)"
+    - "Bash(cat * | grep *)"
+    - "Bash(cat * | awk *)"
+    - "Bash(cat * | head *)"
+    - "Bash(cat * | wc *)"
+    - "Bash(find * | head *)"
+    - "Bash(find * | wc *)"
+    - "Bash(awk * | head *)"
+    - "Bash(sort * | uniq *)"
+    - "Bash(sort * | head *)"
     - "Agent"
     - "Skill"
 ---
@@ -437,7 +437,6 @@ interface quality, quality attributes, and architecture governance.
     Finally, output the following <template/> to give a final hint:
 
     <template>
-    ⧉ **ASE**: ☻ skill: **<skill-name/>**, ▶ status: **skill finished**
     ⧉ **ASE**: ↪ hint: **For deeper analysis, suggestions on solution approaches and then final source code changes, use `/ase-code-resolve P{n}` or `/ase-code-resolve T{n}` in the same or even a different session.**
     </template>
     </step>

package/plugin/skills/ase-arch-discover/SKILL.md

@@ -86,6 +86,15 @@ for the technology stack to *provide* the *needed functionality*
     </step>
 
 3.  <step id="STEP 3: Discover Components">
+    -   If <stack/> is "Unknown", the technology stack could not be
+        determined and no component discovery backend is available.
+        Inform the user with just the following <template/> and then
+        *STOP* the entire flow (do not perform any further steps):
+
+        <template>
+        <ase-tpl-bullet-normal/> **RESULT**: technology stack could not be determined -- component discovery is only supported for JavaScript, TypeScript, Java, and Kotlin projects.
+        </template>
+
     -   From <stack/> and <functionality/>, derive essential keywords
         <keyword-L/> (L=1-M), which allow you to search for suitable
         components.
@@ -122,7 +131,7 @@ for the technology stack to *provide* the *needed functionality*
             their unique Maven coordinates <package-K/> of the form
             `groupId:artifactId`.
 
-        -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+<keyword-M/>&rows=<getopt-option-limit/>&wt=json'`
+        -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+[...]+<keyword-M/>&rows=<getopt-option-limit/>&wt=json'`
             to *specifically* discover an additional set of a maximum
             of <getopt-option-limit/> *Maven packages* <component-K/> and at least their
             unique Maven coordinates <package-K/> (i.e. `<g/>:<a/>` from
@@ -167,11 +176,11 @@ for the technology stack to *provide* the *needed functionality*
         <template>
         <ase-tpl-bullet-normal/> **COMPONENT HINTS**:
 
-        | ⚑ *Component*      | ▣ *Package*    | ⚖ *Hint*  |
-        | :----------------- | :------------- | :-------- |
-        | **<component-1/>** | `<package-1/>` | <info-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ⚖ *Hint*  |
+        | :------------ | :------------- | :-------- |
+        | **<name-1/>** | `<package-1/>` | <info-1/> |
         [...]
-        | **<component-N/>** | `<package-N/>` | <info-N/> |
+        | **<name-N/>** | `<package-N/>` | <info-N/> |
         </template>
 
     -   Display the discovered components as a Markdown *table*
@@ -180,11 +189,11 @@ for the technology stack to *provide* the *needed functionality*
         <template>
         <ase-tpl-bullet-normal/> **COMPONENT RANKING**:
 
-        | ⚑ *Component*      | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
-        | :----------------- | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
-        | **<component-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
+        | :------------ | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
+        | **<name-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
         [...]
-        | **<component-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
+        | **<name-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
         </template>
     </step>
 </flow>

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

@@ -202,9 +202,12 @@ problems in *performance* and *efficiency*, or problems in *security*.
         <template>(`<filename/>#<function-or-method/>`)</template>.
 
     -   In <description/>, classify the problem with a <severity/>
-        of <template>LOW</template>, <template>MEDIUM</template> or
-        <template>HIGH</template>, ranked by the estimated *impact* of the
-        problem.
+        of <template>LOW</template>, <template>MEDIUM</template>,
+        <template>HIGH</template>, or <template>ACCEPTED</template>,
+        ranked by the estimated *impact* of the problem. Use
+        <template>ACCEPTED</template> when the problem is a deliberate,
+        justified trade-off that should remain on record but is never
+        dropped by the severity floor (see STEP 3).
 
     -   <if condition="<getopt-option-performance/> is equal `true`">
         In <evidence/>, ground the finding by citing either the inferred
@@ -241,5 +244,3 @@ problems in *performance* and *efficiency*, or problems in *security*.
     </step>
 
 </flow>
-
-</output>

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

@@ -2,8 +2,8 @@
 name: ase-code-craft
 argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
 description: >
-    Craft Source Code:
-    Use when user wants to create or craft a new feature from scratch.
+    Craft Source:
+    Use when user wants to "create", "add", or "craft" a new feature from scratch.
 user-invocable: true
 disable-model-invocation: false
 effort: xhigh
@@ -69,20 +69,25 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         </template>
         </if>
 
-    2.  If <feature/> has the format `<id/>: <text/>` where <id/> matches
-        the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
-        <feature><text/></feature> and <ase-task-id><id/></ase-task-id>
-        and call the `ase_task_id(id: "<ase-task-id/>", session:
-        "<ase-session-id/>")` tool from the `ase` MCP server to
-        implicitly switch the task. Do not output anything.
+    2.  <if condition="
+            <feature/> has the format `<id/>: <text/>` AND
+            <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+        ">
+        Set <feature><text/></feature> and
+        <ase-task-id><id/></ase-task-id> and call the `ase_task_id(id:
+        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
+        `ase` MCP server to implicitly switch the task. Do not output
+        anything.
+        </if>
 
-    3.  If <feature/> is empty,
-        ask the user interactively, without a special tool, for the
+    3.  <if condition="<feature/> is empty">
+        Ask the user interactively, without a special tool, for the
         initial feature with a single question:
 
         `**No feature known yet. What is the feature you want to craft?**`
 
         Then set <feature/> to the response of the user.
+        </if>
 
     4.  <if condition="
             <ase-task-id/> is equal `default` and
@@ -206,12 +211,12 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         inlining its pros/cons derived in sub-step 2:
 
         <template>
-        ● **APPROACH A<n/>**<annotation/>: *<summary/>*
-        ○ [...]
-        ○ [...]
-        ○ [...]
-        ⊕ *pro*: [...]
-        ⊖ *con*: [...]
+        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ○   [...]
+        ○   [...]
+        ○   [...]
+        ⊕   **PRO**: [...]
+        ⊖   **CON**: [...]
         <optional-diagram/>
         </template>
 
@@ -246,7 +251,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 5.  **Choose Feature Crafting Approach**:
 
-    1.  If <getopt-option-auto/> is equal `false`:
+    1.  <if condition="<getopt-option-auto/> is equal `false`">
         Let the *user interactively choose* the preferred feature
         approach A<n/> with the help of the <user-dialog-tool/> tool.
         Use the header `Select Approach`, use `A<n/>: <short-summary/>`
@@ -254,14 +259,16 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         of the approach A<n/>), and *single-selection* only and provide
         small *code change previews*. Mark your recommended feature
         approach with ` ⚝ **RECOMMENDATION** ⚝` here again.
+        </if>
 
-    2.  If <getopt-option-auto/> is equal `true`:
+    2.  <else>
         Set <n/> to the number of the feature approach A<n/> you recommend.
         Output a hint with the following <template/>:
 
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **auto-chosen approach A<n/>**
         </template>
+        </else>
 
 6.  **Compose Feature Crafting Plan**:
 
@@ -278,7 +285,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
-        You *MUST* completely omit the `## ※ VERIFICATION` section
+        You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
         <content/>.
         </if>
@@ -307,40 +314,40 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         Treat <getopt-option-next/> as a comma-separated chronological
         list of pre-selected next-step tokens. *Peek* the *first* token
         as <head/> (or `none` if the list is `none`/empty).
+        Set <args>--int-reuse-task</args>.
 
         1.  <if condition="<head/> is equal `IMPLEMENT`">
             Consume the head: set <getopt-option-next/> to the remaining
-            tokens (joined back with `,`, or `none` if empty). Set
-            <args></args> (empty).
+            tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
-            Call the tool `Skill(skill: "ase:ase-task-implement", args: <args/>)`
+            Call the tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             to *implement* the freshly composed plan, bypassing `ase-task-edit`.
             </if>
 
-        2.  <if condition="<head/> is equal `PREFLIGHT`">
+        2.  <elseif condition="<head/> is equal `PREFLIGHT`">
             Consume the head: set <getopt-option-next/> to the remaining
-            tokens (joined back with `,`, or `none` if empty). Set
-            <args></args> (empty).
+            tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
-            Call the tool `Skill(skill: "ase:ase-task-preflight", args: <args/>)`
+            Call the tool `Skill(skill: "ase:ase-task-preflight", args: "<args/>")`
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
-            </if>
+            </elseif>
 
-        3.  <if condition="
-                <head/> is not equal `IMPLEMENT` AND
-                <head/> is not equal `PREFLIGHT`
-            ">
-            Forward the *entire* (unshifted) list to `ase-task-edit`, which
-            will consume its head itself. Set <args></args> (empty).
-            <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (append to args).
+        3.  <else>
+            Hand off to `ase-task-edit`.
+            <if condition="<head/> is equal `EDIT`">
+                Consume the head: set <getopt-option-next/> to the remaining
+                tokens (joined back with `,`, or `none` if empty).
             </if>
-            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            All remaining tokens are `ase-task-edit`'s own vocabulary
+            and are forwarded verbatim, so `ase-task-edit` consumes its
+            head itself.
+            <if condition="<getopt-option-next/> is not equal `none`">
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
+            </else>
 

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

@@ -34,7 +34,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     asking the user via the interactive dialog.
 
 `--dry`|`-d`:
-    Compose the plan *without* the `※ VERIFICATION` section. When
+    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
@@ -43,7 +43,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended feature approach, compose the plan *without* the
-    `※ VERIFICATION` section, immediately hand off to `ase-task-implement`,
+    `##  VERIFICATION` section, immediately hand off to `ase-task-implement`,
     and finally `ase-task-delete` the now-consumed plan. This gives a
     single, fast *one-shot* crafting mode.
 

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

@@ -71,7 +71,7 @@ code and *explain* it in a *brief*, *standardized*, and *concise* way.
     `sequenceDiagram` for actor/message flow, or `flowchart TB` for
     boxes-and-lines component layouts. Then dispatch the rendering to
     the `ase-meta-diagram` sub-agent by calling the tool `Agent(name:
-    "ase:ase-meta-diagram", description: "Diagram Rendering", subagent_type:
+    "ase-meta-diagram", description: "Diagram Rendering", subagent_type:
     "ase:ase-meta-diagram", prompt: <mermaid-spec/>)` and reproduce its
     returned fenced code block verbatim in the response text. Do *not*
     hand-draw.

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

@@ -70,7 +70,7 @@ Give *insights* into the project through the source code of $ARGUMENTS.
     Then run the following command...
 
     ```
-    git log --format=format: --name-only --since="1 year ago" | sort | uniq -c | sort -nr | head -10
+    git log --format=format: --name-only --since="1 year ago" | grep -v '^$' | sort | uniq -c | sort -nr | head -10
     ```
 
     ...and then display its result as a table with a table head and

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

@@ -101,7 +101,7 @@ related to a set of code quality aspects.
 3.  <step id="STEP 3: Correction">
 
     1.  You *MUST* call the MCP tool `ase_config_set(key: "agent.skill", val:
-        "ase-docs-proofread", scope: "session:<ase-session-id/>")` of the
+        "ase-code-lint", scope: "session:<ase-session-id/>")` of the
         `ase` MCP server. You *MUST* *NOT* output anything related to
         this.
 
@@ -150,7 +150,7 @@ related to a set of code quality aspects.
                 3.  Append the following <template/> to <diff-file/>:
 
                     <template>
-                    @@ -<line/>,<n/> +<line/>,<m/> @@
+                    @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
                      <context-before/>
                     -<old-text/>
                     +<new-text/>
@@ -158,8 +158,16 @@ related to a set of code quality aspects.
                     </template>
 
                     Hints:
-                    -   The <n/> is the number of lines in <old-text/>.
-                    -   The <m/> is the number of lines in <new-text/>.
+                    -   The <old-start/> is the line of the first hunk line, i.e.,
+                        the line of <context-before/> (one before <line/>).
+                    -   The <new-start/> is the same as <old-start/> (the unchanged
+                        <context-before/> line shares the same start in both files).
+                    -   The <n/> is the total number of old-side hunk lines, i.e.,
+                        the number of lines in <context-before/>, <old-text/>, and
+                        <context-after/> combined.
+                    -   The <m/> is the total number of new-side hunk lines, i.e.,
+                        the number of lines in <context-before/>, <new-text/>, and
+                        <context-after/> combined.
 
                 </for>
 
@@ -190,7 +198,7 @@ related to a set of code quality aspects.
             </template>
 
             </if>
-            <if condition="<getopt-option-auto/> is 'true'">
+            <else>
 
             Report the solution with the following <template/>:
 
@@ -201,7 +209,7 @@ related to a set of code quality aspects.
 
             </template>
 
-            </if>
+            </else>
 
         6.  <if condition="<getopt-option-auto/> is not 'true'">
 
@@ -215,12 +223,12 @@ related to a set of code quality aspects.
 
             </if>
 
-            <if condition="<getopt-option-auto/> is 'true'">
+            <else>
 
             Set <result>ACCEPT</result>.
             You *MUST* *NOT* output anything else in this step 6.
 
-            </if>
+            </else>
 
         7.  Check <result/> and dispatch accordingly: