@rse/ase 0.9.9 → 0.9.11

package/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.9",
+    "version":                              "0.9.11",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.9",
+    "version":     "0.9.11",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.9",
+    "version":     "0.9.11",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/meta/ase-dialog.md

@@ -11,6 +11,7 @@ User Dialog
 </if>
 
 <define name="user-dialog">
+
 Let the *user interactively choose* an answer.
 
 1.  Take the following question specification:
@@ -140,13 +141,17 @@ Let the *user interactively choose* an answer.
 </define>
 
 <define name="custom-dialog">
-Let the *user interactively choose* an answer.
+
+In the following, you *MUST* *NOT* use the <user-dialog-tool/> tool!
+Instead, you *MUST* just show a custom output, let the user enter input,
+and then you set the result accordingly. For this, closely follow the
+following procedure:
 
 1.  Take the following question specification:
+    <spec><content/></spec>
 
-    <spec>
-        <content/>
-    </spec>
+    Take the following options:
+    <opts><arg1/></opts>
 
     The first line of <spec/> (separated by newlines) is of the format:
     `<question-label/>: <question-description/>`
@@ -166,13 +171,17 @@ Let the *user interactively choose* an answer.
 
         Set <text></text> (set to empty).
         Set <keys></keys> (set to empty).
-        Set <n>1</n> (set entry count to one).
-        Set <width/> to the maximum length plus 3 of all <label/> strings in <spec/>.
+        Set <n>0</n> (set entry count to zero).
+        Set <width/> to the maximum length plus 3 of the <label/> strings in the
+        contiguous answer lines of <spec/> starting at line 2 (the answer labels only,
+        excluding the question label on line 1, and stopping at the first missing line --
+        the same lines the entry loop below renders).
 
         <for items="2 3 4 5 6 7 8 9">
             Take from <spec/> the line number <item/>.
             If this line does not exist, <break/>.
             If this line exists, parse it according to the format `<label/>: <description/>`.
+            Set <n/> to <n/> + 1 (increment entry count).
             Set <label-key/> to <ase-tpl-key digit="<n/>"/>.
             Set <label-text/> to `<ase-tpl-pad width="<width/>" text="<label/>:"/>`.
             Append an entry to <text/>:
@@ -182,7 +191,6 @@ Let the *user interactively choose* an answer.
             <ase-tpl-boxline><label-key/>  ▶  **<label-text/>** <description/></ase-tpl-boxline>
             </text>
 
-            Set <n/> to <n/> + 1 (increment entry count).
             <if condition="<keys/> is empty">
                 Set <keys><label-key/></keys>
             </if>
@@ -191,47 +199,67 @@ Let the *user interactively choose* an answer.
             </else>
         </for>
 
+        <if condition="<opts/> contains `--other`">
+            Set <hint>Please choose *one* option by typing <keys/>/**CANCEL**, or other free-text instruction.</hint>.
+        </if>
+        <else>
+            Set <hint>Please choose *one* option by typing <keys/>/**CANCEL**.</hint>.
+        </else>
+
         Set:
 
         <text>
-        <ase-tpl-boxed title="QUESTION" subtitle="<question-label/>">
+        <ase-tpl-boxed title="DIALOG" subtitle="<question-label/>">
 
         <ase-tpl-boxline>**<question-description/>**</ase-tpl-boxline>
 
         <text/>
 
-        Please choose *one* option by typing <keys/>/**CANCEL** or free-text instruction.
+        <hint/>
 
         </ase-tpl-boxed>
         </text>
 
-        If <n/> is less than 3:
-        Set <result>ERROR: user-dialog requires 2-8 answer lines, got less</result>
-        and *SKIP* the following step 2 and continue with step 3 dispatch.
+        If <n/> is less than 2:
+        Set <result>ERROR: custom-dialog requires 2-8 answer lines, got <n/></result>
+        and *SKIP* the following step 2.2 and continue with step 2.3 dispatch.
 
     2.  Output the following <template/>, end the current turn, wait for the
-        user input, store the user input in <result/> and then continue with step 3:
+        user input, store the user input in <result/> and then continue with
+        step 2.3 below:
 
         <template>
         <text/>
         </template>
 
-    3.  Check the result and dispatch accordingly:
+    3.  Do not output anything in this step!
+        Check the <result/> and dispatch accordingly:
 
-        -   If <result/> indicates that the user doesn't want to proceed,
-            or the user declined to answer the question, or that the dialog
-            was cancelled, rejected or skipped, set <result>CANCEL</result>.
+        1.  If <result/> is `cancel`, `CANCEL`, `reject`, `REJECT`, or
+            otherwise indicates that the user doesn't want to proceed,
+            or the user declined to answer the question, or that
+            the dialog was cancelled, rejected or skipped, set
+            <result>CANCEL</result>.
 
-        -   Otherwise, determine the selected <label/>
+        2.  Otherwise, determine the selected <label/>
             by mapping the <result/> (usually containing one of the
-            "key" or "label" strings) to one of the answer labels. Set
-            <result><label/></result>.
+            "key" or "label" strings) to one of the answer labels in
+            <spec/>. Set <result><label/></result>.
 
-            If <result/> is then *NOT* one of the "label" values from
-            <spec/>, set <result>OTHER: <result/></result> (prefix
-            result with "OTHER").
+        3.  If <result/> is then *NEITHER* one of the "key"
+            *NOR* "label" values from <spec/>:
+            <if condition="<opts/> contains `--other`">
+                Set <result>OTHER: <result/></result>
+                (prefix result with "OTHER").
+            </if>
+            <else>
+                Output the following <template/> and then *START OVER*
+                by *GOING* to step 2.2 above.
 
-        Do not output anything in this step!
+                <template>
+                ⧉ **ASE**: ERROR: **Invalid option selected!**
+                </template>
+            </else>
 
 </define>
 

package/plugin/meta/ase-format-arch.md

@@ -77,14 +77,14 @@ distinct **Artifact**s (listed under their <artifact-name/> and their
 The **Artifact**s have the following cross-references:
 
 ```text
-ARCH-02-FV Functionality View   ──(depends on)─► ARCH-02-FV Functionality View
-ARCH-03-IV Information View     ──(entity)─►     SPEC-05-DM Data Model
+ARCH-02-FV Functionality View   ──(depends on)─► ARCH-01-CV Context View
+ARCH-03-IV Information View     ──(entity)─►     SPEC-07-DM Data Model
 ARCH-03-IV Information View     ──(owner)─►      ARCH-02-FV Functionality View
 ARCH-04-CO Concurrency View     ──(hosts)─►      ARCH-02-FV Functionality View
 ARCH-06-DP Deployment View      ──(hosts)─►      ARCH-02-FV Functionality View
 ARCH-07-OV Operations View      ──(element)─►    ARCH-02-FV Functionality View
 ARCH-07-OV Operations View      ──(element)─►    ARCH-06-DP Deployment View
-ARCH-08-QP Quality Perspectives ──(addresses)─►  SPEC-04-NR Non-Functional Requirements
+ARCH-08-QP Quality Perspectives ──(addresses)─►  SPEC-05-NR Non-Functional Requirements
 ARCH-08-QP Quality Perspectives ──(affects)─►    ARCH-02-FV Functionality View
 ARCH-08-QP Quality Perspectives ──(affects)─►    ARCH-06-DP Deployment View
 ARCH-09-DR Decision Record      ──(affects)─►    ARCH-02-FV Functionality View

package/plugin/meta/ase-format-spec.md

@@ -563,7 +563,7 @@ manages, defining how information is organized and connected.
 
     ### RELATIONS
 
-    -   `<spec-dm-relation-id/>`: [`<spec-dm-relation-target/>`](#<spec-dm-relation-id/>)(`<spec-dm-relation-cardinality/>`):<br/>
+    -   `<spec-dm-relation-id/>`: [`<spec-dm-relation-target/>`](#<spec-dm-relation-target-id/>)(`<spec-dm-relation-cardinality/>`):<br/>
         <spec-dm-relation-description/>,
         **BECAUSE** <spec-dm-relation-rationale/>.
 
@@ -615,7 +615,7 @@ manages, defining how information is organized and connected.
     -   <spec-dm-relation-target/>: the <spec-dm-entity-name/> of the
         entity the directed relation targets.
 
-    -   <spec-dm-relation-id/>: the <spec-dm-entity-id/> of the
+    -   <spec-dm-relation-target-id/>: the <spec-dm-entity-id/> of the
         entity the directed relation targets.
 
     -   <spec-dm-relation-cardinality/>: the cardinality of the entity
@@ -724,8 +724,17 @@ making the forbidden moves as explicit as the allowed ones.
         is implicitly forbidden.
 
     -   Every <spec-sm-state-name/> used in a transition *MUST* be
-        declared in the `### STATES` block, and every non-final state
-        *MUST* have at least one outgoing transition.
+        declared in the `### STATES` block, and every state with no
+        outgoing transition *MUST* be listed in <spec-sm-lifecycle-final/>
+        (a state with no outgoing transition that is not final would be a
+        stuck dead-end). The converse does *not* hold: a
+        <spec-sm-lifecycle-final/> state *MAY* still have outgoing
+        transitions, modeling a resting state that can later be left again
+        (e.g. a `Closed` state with a `reopen` transition back to
+        `Active`). Thus <spec-sm-lifecycle-final/> designates the states in
+        which the entity may legally come to rest, which is a superset of,
+        but not necessarily equal to, the set of declared states that have
+        no outgoing transition.
 
     -   In case a transition has no side effect, the
         entire `<spec-sm-transition-effect/>,` clause is omitted.

package/plugin/meta/ase-getopt.md

@@ -26,8 +26,10 @@ set placeholders into the context as a side-effect.
         For each option token in <getopt-spec/> of the form
         `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)[...]]`, set
         <getopt-option-<long/>/> to <default/> (for `=<default/>`
-        form), or to <c1/> (the first choice, for `=(<c1/>|<c2>/|...)`
-        form, or for the list form `=(<c1/>|<c2>/|...)...`),
+        form), or to the *single token* <c1/> (the first choice, both
+        for the choice form `=(<c1/>|<c2>/|...)` and for the list form
+        `=(<c1/>|<c2>/|...)...` -- an *unsupplied* list-option always
+        defaults to the single token <c1/>, *not* to a whole list),
         or to `false` (for value-less options). Then set
         <getopt-arguments><getopt-args/></getopt-arguments>.
 
@@ -52,11 +54,13 @@ set placeholders into the context as a side-effect.
     `=(<c1>|<c2>|...)` declares a value-taking option restricted to the
     listed fixed choices (the first choice acts as the default), and the
     trailing `...` (as in `=(<c1>|<c2>|...)...`) declares a value-taking
-    option whose value is a *comma-separated list* of choice tokens
-    (the first choice still acts as the default; only the *first*
-    token of the list is validated by the parser against the choice
-    set -- subsequent tokens are *not* validated, and skills validate
-    each remaining token themselves as they consume it).
+    option whose *supplied* value is a *comma-separated list* of choice
+    tokens (when *unsupplied*, the option defaults to the *single
+    token* `<c1>`, identical to the non-list choice form -- the list
+    semantics apply only to an explicitly supplied value; only the
+    *first* token of a supplied list is validated by the parser against
+    the choice set -- subsequent tokens are *not* validated, and skills
+    validate each remaining token themselves as they consume it).
 
 4.  **Short-Circuit for Error**:
     If <text/> starts with `ERROR:`:

package/plugin/meta/ase-skill.md

@@ -215,6 +215,11 @@ Skill Identification
     @${CLAUDE_SKILL_DIR}/help.md
     </template>
 
+-   *IMPORTANT*:
+    You *MUST* *NOT* output any summaries, explanations, or next
+    steps at the end of a skill beside the explicit outputs via any
+    <template/>.
+
 Template Patterns
 -----------------
 
@@ -227,12 +232,13 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-head title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (67 - length("⧉ ASE: <title/>")), i.e., <bar/> is
-    the "─" character repeated (67 - length("⧉ ASE: <title/>")) times):
+    (where <title-len/> is the number of characters in the string
+    `⧉ ASE: <title/>`, and <bar/> is the `─` character repeated exactly
+    (67 - <title-len/>) times):
 
     <template>
 
-    ╭────━━━━**(** `⧉ ASE`: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╭────━━━━**(** ⧉ ASE: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
@@ -245,12 +251,13 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-foot title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (67 - length("⧉ ASE: <title/>")), i.e., <bar/> is
-    the "─" character repeated (67 - length("⧉ ASE: <title/>")) times):
+    (where <title-len/> is the number of characters in the string
+    `⧉ ASE: <title/>`, and <bar/> is the `─` character repeated exactly
+    (67 - <title-len/>) times):
 
     <template>
 
-    ╰────━━━━**(** `⧉ ASE`: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╰────━━━━**(** ⧉ ASE: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
@@ -272,14 +279,14 @@ Template Patterns
 
     -   <if condition="<subtitle/> is not empty">
             Set <raw-title>⧉ ASE: <title/>: <subtitle/><raw-title>.
-            Set <render-title>`⧉ ASE`: **`<title/>`**: `<subtitle/>`</render-title>.
+            Set <render-title>⧉ ASE: **`<title/>`**: `<subtitle/>`</render-title>.
         </if>
         <else>
             Set <raw-title>⧉ ASE: <title/><raw-title>.
-            Set <render-title>`⧉ ASE`: **`<title/>`**</render-title>.
+            Set <render-title>⧉ ASE: **`<title/>`**</render-title>.
         </else>
-    -   Set <bar/> to ("─" x (67 - length("<raw-title/>"))),
-        i.e., set <bar/> to the "─" character repeated (67 - length("<raw-title/>")) times.
+    -   Set <raw-title-len/> to the number of characters in <raw-title/>.
+    -   Set <bar/> to the `─` character repeated exactly (67 - <raw-title-len/>) times.
     -   Set <body> to <content/> with all line-starts prefixed with `│ `.
 
     <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.9",
+    "version":                              "0.9.11",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -101,14 +101,19 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-arch-analyze">
 Review Software Architecture
 </skill>
 
+<expand name="getopt" arg1="ase-arch-analyze">
+    $ARGUMENTS
+</expand>
+
 <objective>
 With the mindset of an *expert-level software architect*,
-*review* the *software architecture* of $ARGUMENTS, and its directly
+*review* the *software architecture* of <getopt-arguments/>, and its directly
 related source code, for *potential problems* across component
 boundaries, structural organization, architecture principles,
 interface quality, quality attributes, and architecture governance.

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

@@ -42,15 +42,18 @@ for the technology stack to *provide* the *needed functionality*
 
     2.  If <functionality/> is not clear, not precise, or not specific
         enough, let the *user interactively choose* the intended
-        functionality. For this you *MUST* use the custom `custom-dialog`
-        and *NOT* the `AskUserQuestion` based "user-dialog":
+        functionality.
 
-        <expand name="custom-dialog">
+        In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+        tool! Instead, you *MUST* just show a custom output, let the
+        user enter input, and then you set the result accordingly.
+
+        <expand name="custom-dialog" arg1="--no-other">
             Functionality: Which functionality should the components provide?
             <answer-1/>: (grounded candidate functionality 1)
             <answer-2/>: (grounded candidate functionality 2)
-            <answer-3/>: (grounded candidate functionality 2)
-            <answer-4/>: (grounded candidate functionality 3)
+            <answer-3/>: (grounded candidate functionality 3)
+            <answer-4/>: (grounded candidate functionality 4)
         </expand>
 
         Then use the <result/> and its corresponding grounded candidate
@@ -112,7 +115,7 @@ for the technology stack to *provide* the *needed functionality*
         <keyword-L/> (L=1-M), which allow you to search for suitable
         components.
 
-    3.. In the to be discovered result set of components <component-K/>
+    3.  In the to be discovered result set of components <component-K/>
         (K=1-N), remember the component name as <name-K/>, the
         official package name as <package-K/>, the latest version as
         <version-K/>, the stars as <stars-K/>, the created date as

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

@@ -40,7 +40,8 @@ problems in *performance* and *efficiency*, or problems in *security*.
 
     <if condition="<getopt-option-performance/> is equal `true` and <getopt-option-security/> is equal `true`">
 
-    Only output the following <template/> and then *STOP* immediately:
+    Only output the following <template/> and then *STOP* the entire flow
+    (do not perform any further steps):
 
     <template>
     ⧉ **ASE**: ✪ skill: **ase-code-analyze**, ▶ ERROR: options `--performance` and `--security` are mutually exclusive
@@ -146,10 +147,12 @@ problems in *performance* and *efficiency*, or problems in *security*.
     than or equal to `rank(<getopt-option-severity/>)`; *silently drop*
     all other problems (they are neither reported nor persisted). With
     the default floor `LOW`, all problems are kept. `ACCEPTED` problems
-    are *never* dropped. Then renumber the surviving problems
-    contiguously as `P<n/>` with <n/> = 1, 2, ... in the original
-    ordering. If *all* problems are dropped, skip the per-problem report
-    but still emit the final hint <template/> below.
+    are *never* dropped.
+
+    Then renumber the surviving problems contiguously as `P<n/>` with
+    <n/> = 1, 2, ... in the original ordering. If *all* problems are
+    dropped, skip the per-problem report but still emit the final hint
+    <template/> below.
 
     In this STEP 3, for *EVERY* surviving problem, immediately report
     it with the following output <template/>, based on concise bullet
@@ -209,6 +212,10 @@ problems in *performance* and *efficiency*, or problems in *security*.
         justified trade-off that should remain on record but is never
         dropped by the severity floor (see STEP 3).
 
+    -   For <title/> ultra-compress the <description/> to a concise,
+        short, single sentence. Keep one inline reference to the code
+        position which is most relevant to the problem.
+
     -   <if condition="<getopt-option-performance/> is equal `true`">
         In <evidence/>, ground the finding by citing either the inferred
         *Big-O* time/space complexity (e.g. `O(n²)` reducible to `O(n)`)

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

@@ -220,10 +220,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ●   **APPROACH A<n/>**<annotation/>: **<summary/>**
         ○   [...]
-        ⊕   **PRO**: [...]
-        ⊖   **CON**: [...]
+        ⊕   *PRO*: [...]
+        ⊖   *CON*: [...]
         </template>
 
         Hints:
@@ -241,18 +241,19 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     7.  <if condition="<getopt-option-auto/> is not equal `true`">
 
-        You *MUST* use the custom `custom-dialog` and *NOT* the
-        `AskUserQuestion`-based `user-dialog` to let the *user
-        interactively choose* the preferred approach A<n/>.
+        In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+        tool! Instead, you *MUST* just show a custom output, let the
+        user enter input, and then you set the result accordingly.
 
-        Per approach A<n/>, use the option `A<n/>: <short-summary/>`
-        where <short-summary/> is an ultra brief summary of the approach
-        A<n/>. For your recommended approach, use
-        `A<n/>: ⚝ **RECOMMENDATION** ⚝: <short-summary/>` instead.
+        Let the user choose the preferred approach A<n/> by raising
+        a question with the following custom dialog, where per
+        approach A<n/>, you determine an ultra brief summary
+        <short-summary/> and then use the answer option `A<n/>:
+        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        recommended approach plus zero or more answer options `A<n/>:
+        <short-summary/>` for all other approaches:
 
-        Now raise the user dialog:
-
-        <expand name="custom-dialog">
+        <expand name="custom-dialog" arg1="--no-other">
             Select Approach: Select your preferred crafting approach to follow?
             A<n/>: <short-summary/>
             [...]
@@ -342,17 +343,20 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             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).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own 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>
 
-    <step>
+    </step>
 
 </flow>

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

@@ -14,13 +14,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-explain">
 Explain Source Code
 </skill>
 
+<expand name="getopt" arg1="ase-code-explain">
+    $ARGUMENTS
+</expand>
+
 <objective>
-*Analyze* the source code of $ARGUMENTS, and its directly related source
+*Analyze* the source code of <getopt-arguments/>, and its directly related source
 code and *explain* it in a *brief*, *standardized*, and *concise* way.
 </objective>
 

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

@@ -7,23 +7,29 @@ user-invocable: true
 disable-model-invocation: false
 effort: high
 allowed-tools:
-    - "Bash(git)"
-    - "Bash(sort)"
-    - "Bash(uniq)"
-    - "Bash(head)"
+    - "Bash(git *)"
+    - "Bash(grep *)"
+    - "Bash(sort *)"
+    - "Bash(uniq *)"
+    - "Bash(head *)"
     - "Skill"
     - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-insight">
 Project Insight
 </skill>
 
+<expand name="getopt" arg1="ase-code-insight">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Give *insights* into the project through the source code of $ARGUMENTS.
+Give *insights* into the project through the source code of <getopt-arguments/>.
 </objective>
 
 <flow>

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

@@ -152,7 +152,7 @@ related to a set of code quality aspects.
                 3.  Append the following <template/> to <diff-file/>:
 
                     <template>
-                    @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
+                    @@ -<old-start/>,<old-count/> +<new-start/>,<new-count/> @@
                      <context-before/>
                     -<old-text/>
                     +<new-text/>
@@ -164,10 +164,10 @@ related to a set of code quality aspects.
                         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 <old-count/> 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 <new-count/> is the total number of new-side hunk lines, i.e.,
                         the number of lines in <context-before/>, <new-text/>, and
                         <context-after/> combined.
 
@@ -215,11 +215,11 @@ related to a set of code quality aspects.
 
         6.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Let the *user interactively choose* what to do as the next
-            step. For this you *MUST* use the custom `custom-dialog` and
-            not the `AskUserQuestion` based `user-dialog`:
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
 
-            <expand name="custom-dialog">
+            <expand name="custom-dialog" arg1="--other">
                 CORRECTION: How would you like to proceed with this proposed correction?
                 ACCEPT: Apply the proposed correction.
                 REJECT: Skip this proposed correction.
@@ -248,9 +248,15 @@ related to a set of code quality aspects.
             -   <if condition="<result/> starts with 'OTHER'">
                 Generate a *new* proposal for the *same* <item/>
                 (incorporating the user's free-text hint from <result/> if
-                provided via 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`.
+                provided via the "OTHER" prefix). *Reassign* <description/>
+                and <change-set/> to reflect this refined proposal (each
+                change-hunk's `old_text` stays anchored to the existing
+                text at its `file`:`line`; `new_text` carries the
+                refinement) so that the substep 2/3 rebuild renders the new
+                <diff/> and any `Edit` applies the new proposal rather than
+                the original. Then 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="