@rse/ase 0.9.44 → 0.9.46

package/plugin/meta/ase-tenets.md

@@ -5,7 +5,7 @@ ASE Tenets
 The following are the **ASE Tenets** -- the guiding principles you
 *MUST* internalize when requested. They are organized into *Generic
 Tenets*, which always apply, and *Operation-Specific Tenets*, which
-apply only to a particular kind of operation (Crafting, Aligning,
+apply only to a particular kind of operation (Crafting, Reconciling,
 Refactoring, Resolving).
 
 GENERIC TENETS
@@ -80,7 +80,7 @@ CRAFTING TENETS
 ---------------
 
 When *crafting* from scratch a new artifact, a feature, or an aspect,
-you *MUST* honor the following so-called "CRAFTING TENETS":
+you *MUST* honor the following so-called **CRAFTING TENETS**:
 
 -   **Clear Minimal Scope**:
     Establish explicit boundaries for the new feature.
@@ -167,7 +167,7 @@ REFACTORING TENETS
 ------------------
 
 When *refactoring* existing artifacts or aspects,
-you *MUST* honor the following so-called **REFACTORING TENETS**
+you *MUST* honor the following so-called **REFACTORING TENETS**:
 
 -   **Behavior Preservation**:
     Refactoring changes only re-structure, never change any
@@ -200,7 +200,7 @@ RESOLVING TENETS
 ----------------
 
 When *resolving* a problem or challenge (bug-fixing),
-you *MUST* honor the following so-called **RESOLVING TENETS**
+you *MUST* honor the following so-called **RESOLVING TENETS**:
 
 -   **No Cleanups**:
     Strictly focus on resolving the problem and do not mix the task with

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "https://ase.tools",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "https://github.com/rse/ase/issues" },
-    "version":                              "0.9.44",
+    "version":                              "0.9.46",
     "license":                              "Apache-2.0",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -4,7 +4,6 @@ argument-hint: "[--help|-h] <source-reference>"
 description: Review software architecture, including package cohesion and inter-package coupling
 user-invocable: true
 disable-model-invocation: false
-model: opus
 effort: high
 allowed-tools:
     - "Bash(wc *)"
@@ -252,7 +251,7 @@ interface quality, quality attributes, and architecture governance.
       - *god-package*: *incoming ≥ 5* and *outgoing ≥ 3* -
         coordinator dumping ground that should be split along its
         internal topical clusters
-      - *fragment*: 1–2 files under a sibling parent that share a
+      - *fragment*: 1-2 files under a sibling parent that share a
         *name prefix* or *imported interface* with that sibling -
         consolidation candidate
 
@@ -278,7 +277,7 @@ interface quality, quality attributes, and architecture governance.
       which operations sit *between* the specific acquire and
       release in source order.
 
-    - *Package-graph construction (SA19–SA21)*: parse each file's
+    - *Package-graph construction (SA19-SA21)*: parse each file's
       import (or equivalent language construct) statement, keep
       only first-party packages within the analyzed scope, and
       persist two intermediate structures: the per-package

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

@@ -2,7 +2,7 @@
 name: ase-code-craft
 argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
 description: >
-    Craft Source:
+    Craft Source Code:
     Use when user wants to "create", "add", or "craft" a new feature from scratch.
 user-invocable: true
 disable-model-invocation: false
@@ -23,7 +23,7 @@ Craft Source Code
 
 <expand name="getopt"
     arg1="ase-code-craft"
-    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)...">
+    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
     $ARGUMENTS
 </expand>
 
@@ -109,7 +109,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     7.  Ask the user for clarification if the goal of this crafting is too
         unclear.
 
-    8.  Do not output anything in this step, unless you asked the user.
+    8.  Do not output anything else in this step, unless you asked the user.
 
     </step>
 
@@ -231,18 +231,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         closely aligning to the existing architecture and the existing
         code base. Use the <format/> defined for a task plan and inject
         the information from feature A<n/> and all derived realization
-        decisions into it. Store the resulting task plan in <content/>.
+        decisions into it. Store the resulting task plan in <task-content/>.
 
         If a `CHANGELOG.md` file exists in the project (or in any
         affected sub-package), the plan *MUST* include, as part of its
-        `## ※ CHANGES` section, an explicit bullet point describing
+        `##  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/>.
+        <task-content/>.
         </if>
 
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
@@ -253,10 +253,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <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/>.
+        words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
 
     4.  Output a hint with the following <template/>:
 
@@ -303,7 +303,21 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
             </elseif>
 
-        4.  <else>
+        4.  <elseif condition="<head/> is equal `GRILL`">
+            Consume the head: set <getopt-option-next/> to the remaining
+            tokens (joined back with `,`, or `none` if empty). `GRILL`
+            is this skill's own dispatch token, *not* part of
+            `ase-task-grill`'s `--next` vocabulary, so it must be
+            stripped here rather than forwarded. All remaining tokens are
+            `ase-task-grill`'s own vocabulary and are forwarded verbatim.
+            <if condition="<getopt-option-next/> is not equal `none`">
+                Set <args><args/> --next <getopt-option-next/></args>
+            </if>
+            Call the tool `Skill(skill: "ase:ase-task-grill", args: "<args/>")`
+            to *grill* the freshly composed plan, bypassing `ase-task-edit`.
+            </elseif>
+
+        5.  <else>
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining

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

@@ -50,15 +50,16 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--next`|`-n` *option*[,...]:
     Automatically choose the next step after composing the plan.
     *option* is a single token or a *comma-separated chronological
-    list* of tokens; an `IMPLEMENT` or `PREFLIGHT` head token is
-    consumed by this skill (bypassing `ase-task-edit`), and any
+    list* of tokens; an `IMPLEMENT`, `PREFLIGHT`, or `GRILL` head token
+    is consumed by this skill (bypassing `ase-task-edit`), and any
     remaining tokens are *forwarded* (via `--next`) to the downstream
     skill. For all other head tokens, the *entire* list is forwarded
     to `ase-task-edit`, which consumes its head itself. This lets an
     entire pipeline be pre-scripted in one shot. Recognized tokens at
     this skill: `none` (default, hand-off to `ase-task-edit`
     interactively), `DONE` (stop), `EDIT` (hand off to
-    `ase-task-edit`), `PREFLIGHT` (hand off to `ase-task-preflight`),
+    `ase-task-edit`), `GRILL` (hand off to `ase-task-grill`),
+    `PREFLIGHT` (hand off to `ase-task-preflight`),
     or `IMPLEMENT` (hand off to `ase-task-implement`). Example:
     `--next PREFLIGHT,IMPLEMENT,DONE` crafts the plan, preflights it,
     implements it, and exits without further dialog.
@@ -87,4 +88,4 @@ Craft a feature under a named task and directly hand off to implementation:
 ##  SEE ALSO
 
 [`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-task-edit`](../ase-task-edit/help.md),
-[`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).
+[`ase-task-grill`](../ase-task-grill/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -154,11 +154,14 @@ related to a set of code quality aspects.
         still perform substep 3 first. Never leave this marker active
         for a later, unrelated `Edit`.
 
-    2.  Iterate over all problems:
+    2.  Set <total/> to the number of problems in <problems/> and
+        <index/> to `0`. Then iterate over all problems:
 
         <for items="<problems/>">
 
-        1.  Set <aspect/>      to the `aspect`      field of <item/>.
+        1.  Increment <index/> by one (the 1-based position of the
+            current <item/> within <problems/>).
+            Set <aspect/>      to the `aspect`      field of <item/>.
             Set <severity/>    to the `severity`    field of <item/>.
             Set <description/> to the `description` field of <item/>.
             Set <change-set/>  to the `change-set`  field of <item/>.
@@ -193,6 +196,19 @@ related to a set of code quality aspects.
                     Set <new-text/>       to the `new_text`       field of <item/>.
                     Set <context-after/>  to the `context_after`  field of <item/>.
 
+                    Then *normalize* the hunk to its *minimal* form, so
+                    that the proposed diff shows exactly the lines the
+                    later `Edit` will actually change: while the *first*
+                    line of <old-text/> is identical to the *first* line
+                    of <new-text/>, *move* that line from both to the
+                    end of <context-before/> and increment <line/> by
+                    one; likewise, while the *last* line of <old-text/>
+                    is identical to the *last* line of <new-text/>,
+                    *move* that line from both to the front of
+                    <context-after/>. Finally, *trim* <context-before/>
+                    to its *last* two lines and <context-after/> to its
+                    *first* two lines.
+
                 2.  *Skip* this substep entirely when <ase-project-boxing/>
                     is equal `grey` - the full unified diff is suppressed
                     there, so none of the <hunk-body/>, <old-count/>,
@@ -288,7 +304,7 @@ related to a set of code quality aspects.
         4.  Report the problem with the following <template/>:
 
             <template>
-            <ase-tpl-bullet-signal/> **<aspect/> PROBLEM** (`<severity/>`): <context/>
+            <ase-tpl-bullet-signal/> [<index/>/<total/>]: **<aspect/> PROBLEM** (`<severity/>`): <context/>
 
             <description/>
 

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

@@ -18,12 +18,12 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-refactor">
-Refactor Artifacts
+Refactor Source Code
 </skill>
 
 <expand name="getopt"
     arg1="ase-code-refactor"
-    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)...">
+    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
     $ARGUMENTS
 </expand>
 
@@ -109,7 +109,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     7.  Ask the user for clarification if the goal of this refactoring is
         too unclear.
 
-    8.  Do not output anything in this step, unless you asked the user.
+    8.  Do not output anything else in this step, unless you asked the user.
 
     </step>
 
@@ -231,18 +231,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         closely aligning to the existing architecture and the existing
         code base. Use the <format/> defined for a task plan and inject
         the information from refactoring A<n/> and all derived realization
-        decisions into it. Store the resulting task plan in <content/>.
+        decisions into it. Store the resulting task plan in <task-content/>.
 
         If a `CHANGELOG.md` file exists in the project (or in any
         affected sub-package), the plan *MUST* include, as part of its
-        `## ※ CHANGES` section, an explicit bullet point describing
+        `##  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/>.
+        <task-content/>.
         </if>
 
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
@@ -253,10 +253,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <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/>.
+        words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
 
     4.  Output a hint with the following <template/>:
 
@@ -303,7 +303,21 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
             </elseif>
 
-        4.  <else>
+        4.  <elseif condition="<head/> is equal `GRILL`">
+            Consume the head: set <getopt-option-next/> to the remaining
+            tokens (joined back with `,`, or `none` if empty). `GRILL`
+            is this skill's own dispatch token, *not* part of
+            `ase-task-grill`'s `--next` vocabulary, so it must be
+            stripped here rather than forwarded. All remaining tokens are
+            `ase-task-grill`'s own vocabulary and are forwarded verbatim.
+            <if condition="<getopt-option-next/> is not equal `none`">
+                Set <args><args/> --next <getopt-option-next/></args>
+            </if>
+            Call the tool `Skill(skill: "ase:ase-task-grill", args: "<args/>")`
+            to *grill* the freshly composed plan, bypassing `ase-task-edit`.
+            </elseif>
+
+        5.  <else>
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining

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

@@ -50,15 +50,16 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--next`|`-n` *option*[,...]:
     Automatically choose the next step after composing the plan.
     *option* is a single token or a *comma-separated chronological
-    list* of tokens; an `IMPLEMENT` or `PREFLIGHT` head token is
-    consumed by this skill (bypassing `ase-task-edit`), and any
+    list* of tokens; an `IMPLEMENT`, `PREFLIGHT`, or `GRILL` head token
+    is consumed by this skill (bypassing `ase-task-edit`), and any
     remaining tokens are *forwarded* (via `--next`) to the downstream
     skill. For all other head tokens, the *entire* list is forwarded
     to `ase-task-edit`, which consumes its head itself. This lets an
     entire pipeline be pre-scripted in one shot. Recognized tokens at
     this skill: `none` (default, hand off to `ase-task-edit`
     interactively), `DONE` (stop), `EDIT` (hand off to
-    `ase-task-edit`), `PREFLIGHT` (hand off to `ase-task-preflight`),
+    `ase-task-edit`), `GRILL` (hand off to `ase-task-grill`),
+    `PREFLIGHT` (hand off to `ase-task-preflight`),
     or `IMPLEMENT` (hand off to `ase-task-implement`). Example:
     `--next PREFLIGHT,IMPLEMENT,DONE` refactors, preflights, implements,
     and exits without further dialog.
@@ -87,4 +88,4 @@ Refactor under a named task and directly hand off to implementation:
 ##  SEE ALSO
 
 [`ase-code-craft`](../ase-code-craft/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-task-edit`](../ase-task-edit/help.md),
-[`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).
+[`ase-task-grill`](../ase-task-grill/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -23,7 +23,7 @@ Resolve Problem
 
 <expand name="getopt"
     arg1="ase-code-resolve"
-    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)...">
+    arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
     $ARGUMENTS
 </expand>
 
@@ -124,7 +124,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     8.  Ask the user for clarification if the goal of this resolution is
         too unclear.
 
-    9.  Do not output anything in this step, unless you asked the user.
+    9.  Do not output anything else in this step, unless you asked the user.
 
     10. Investigate and *figure out details* related to this problem.
         Report those details with the following <template/>:
@@ -285,18 +285,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         problem, the chosen resolution approach, a preview of the *unified
         diff* of the necessary code changes, and a possible way to verify
         the success of the resolution, by using the <format/> defined for a
-        task plan. Store the resulting task plan in <content/>.
+        task plan. Store the resulting task plan in <task-content/>.
 
         If a `CHANGELOG.md` file exists in the project (or in any
         affected sub-package), the plan *MUST* include, as part of its
-        `## ※ CHANGES` section, an explicit bullet point describing
+        `##  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/>.
+        <task-content/>.
         </if>
 
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
@@ -307,10 +307,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <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/>.
+        words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
 
     4.  If <problem-id/> is set (i.e. the <problem/> was retrieved from
         `ase_kv_get` in STEP 1.1 via key `ase-issue-<problem-id/>`),
@@ -364,7 +364,21 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
             </elseif>
 
-        4.  <else>
+        4.  <elseif condition="<head/> is equal `GRILL`">
+            Consume the head: set <getopt-option-next/> to the remaining
+            tokens (joined back with `,`, or `none` if empty). `GRILL`
+            is this skill's own dispatch token, *not* part of
+            `ase-task-grill`'s `--next` vocabulary, so it must be
+            stripped here rather than forwarded. All remaining tokens are
+            `ase-task-grill`'s own vocabulary and are forwarded verbatim.
+            <if condition="<getopt-option-next/> is not equal `none`">
+                Set <args><args/> --next <getopt-option-next/></args>
+            </if>
+            Call the tool `Skill(skill: "ase:ase-task-grill", args: "<args/>")`
+            to *grill* the freshly composed plan, bypassing `ase-task-edit`.
+            </elseif>
+
+        5.  <else>
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining

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

@@ -55,15 +55,16 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--next`|`-n` *option*[,...]:
     Automatically choose the next step after composing the plan.
     *option* is a single token or a *comma-separated chronological
-    list* of tokens; an `IMPLEMENT` or `PREFLIGHT` head token is
-    consumed by this skill (bypassing `ase-task-edit`), and any
+    list* of tokens; an `IMPLEMENT`, `PREFLIGHT`, or `GRILL` head token
+    is consumed by this skill (bypassing `ase-task-edit`), and any
     remaining tokens are *forwarded* (via `--next`) to the downstream
     skill. For all other head tokens, the *entire* list is forwarded
     to `ase-task-edit`, which consumes its head itself. This lets an
     entire pipeline be pre-scripted in one shot. Recognized tokens at
     this skill: `none` (default, hand off to `ase-task-edit`
     interactively), `DONE` (stop), `EDIT` (hand off to
-    `ase-task-edit`), `PREFLIGHT` (hand off to `ase-task-preflight`),
+    `ase-task-edit`), `GRILL` (hand off to `ase-task-grill`),
+    `PREFLIGHT` (hand off to `ase-task-preflight`),
     or `IMPLEMENT` (hand off to `ase-task-implement`). Example:
     `--next IMPLEMENT,DONE` resolves the problem, implements it, and
     exits without further dialog.
@@ -93,5 +94,5 @@ Resolve a previously analyzed issue and hand off to implementation:
 ##  SEE ALSO
 
 [`ase-code-craft`](../ase-code-craft/help.md), [`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md),
-[`ase-arch-analyze`](../ase-arch-analyze/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md),
-[`ase-task-implement`](../ase-task-implement/help.md).
+[`ase-arch-analyze`](../ase-arch-analyze/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-grill`](../ase-task-grill/help.md),
+[`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -17,7 +17,7 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-docs-distill">
-    Distill Key Points
+Distill Key Points
 </skill>
 
 <expand name="getopt"
@@ -27,11 +27,11 @@ effort: high
 </expand>
 
 <objective>
-    *Distill* the content `<getopt-arguments/>` into a *flat*,
-    *importance-ranked* list of its *key points* - each point an
-    *atomic* claim carrying a *0-10 salience rank*, a *one-line
-    rationale*, and a *verbatim, line-cited evidence* snippet - keeping
-    at most `<getopt-option-top/>` points.
+*Distill* the content `<getopt-arguments/>` into a *flat*,
+*importance-ranked* list of its *key points* - each point an
+*atomic* claim carrying a *0-10 salience rank*, a *one-line
+rationale*, and a *verbatim, line-cited evidence* snippet - keeping
+at most `<getopt-option-top/>` points.
 </objective>
 
 Procedure

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

@@ -135,11 +135,14 @@ Analyze documents for spelling, punctuation, or grammar errors
         still perform substep 3 first. Never leave this marker active
         for a later, unrelated `Edit`.
 
-    2.  Iterate over all problems:
+    2.  Set <total/> to the number of problems in <problems/> and
+        <index/> to `0`. Then iterate over all problems:
 
         <for items="<problems/>">
 
-        1.  Set <type/>           to the `type` field of <item/>.
+        1.  Increment <index/> by one (the 1-based position of the
+            current <item/> within <problems/>).
+            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/>.
@@ -148,10 +151,22 @@ Analyze documents for spelling, punctuation, or grammar errors
             Set <new-text/>       to the `new_text` field of <item/>.
             Set <context-after/>  to the `context_after` field of <item/>.
 
+            Then *normalize* the change to its *minimal* form, so
+            that the proposed diff shows exactly the lines the later
+            `Edit` will actually change: while the *first* line of
+            <old-text/> is identical to the *first* line of
+            <new-text/>, *move* that line from both to the end of
+            <context-before/> and increment <line/> by one; likewise,
+            while the *last* line of <old-text/> is identical to the
+            *last* line of <new-text/>, *move* that line from both to
+            the front of <context-after/>. Finally, *trim*
+            <context-before/> to its *last* two lines and
+            <context-after/> to its *first* two lines.
+
         2.  Report the problem with the following <template/>:
 
             <template>
-            <ase-tpl-bullet-signal/> **<type/> PROBLEM**: `<file/>`:<line/>:
+            <ase-tpl-bullet-signal/> [<index/>/<total/>]: **<type/> PROBLEM**: `<file/>`:<line/>:
 
             <description/>
             </template>

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

@@ -2,7 +2,7 @@
 name: ase-meta-changelog
 argument-hint: "[--help|-h]"
 description: >
-    Update changes entries in CHANGELOG.md files
+    Update ChangeLog entries in CHANGELOG.md files
 user-invocable: true
 disable-model-invocation: false
 effort: high
@@ -108,7 +108,10 @@ Processing
     corresponding Git tag already exists with the command `git tag --list
     N.M.K`. If this command produces *no* output, the first section is
     still in-progress/untagged, so use the `N.M.K` from the *second*
-    level-2 header as the baseline tag instead. If this command *does*
+    level-2 header as the baseline tag instead. If *no* second level-2
+    header exists (very first, still untagged release), skip the baseline
+    tag and check *all* Git commits with the command `git log HEAD
+    --numstat --pretty=format:'%h: %s'` instead. If this command *does*
     produce output, the first section is already released/tagged, so use
     the `N.M.K` from the *first* level-2 header as the baseline tag. Then
     check all Git commits between `HEAD` and this baseline tag with the

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

@@ -48,10 +48,10 @@ currently staged Git changes.
     of the `ase-meta-diff` and `ase-meta-changelog` skills) and their
     usual corresponding kind of change are:
 
-    -   `FEATURE`:     new functionality or configuration
-    -   `IMPROVEMENT`: improved functionality or configuration
-    -   `BUGFIX`:      corrected functionality or configuration
-    -   `UPDATE`:      updated functionality or configuration
+    -   `FEATURE`:     new        functionality or configuration
+    -   `IMPROVEMENT`: improved   functionality or configuration
+    -   `BUGFIX`:      corrected  functionality or configuration
+    -   `UPDATE`:      updated    functionality or configuration
     -   `CLEANUP`:     cleaned up functionality or configuration
     -   `REFACTOR`:    refactored functionality or configuration
 

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

@@ -40,8 +40,8 @@ value until STEP 6. Do not fabricate passes: a probe whose actual result
 differs from its expected result *MUST* be recorded as a *fail*.
 
 Notice that this skill intentionally does not strictly follow the ASE
-skill format, especially it does not include any meta skill information,
-etc.
+skill format; in particular, it does not include the usual meta skill
+information.
 
 Procedure
 ---------
@@ -107,7 +107,7 @@ Procedure
         Record <s/> as actual result for `control-flow/while-sum`.
 
     3.  *for-order*: Set <s></s>, then evaluate
-        `<for items="x y z"><s><s/>-<item/></for>`.
+        `<for items="x y z"><s><s/>-<item/></s></for>`.
         Record <s/> as actual result for `control-flow/for-order`.
 
     4.  *while-break*: Set <i>1</i> and <hit></hit>, then evaluate

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

@@ -103,8 +103,8 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
 
     -   **Argue in Good Faith**:
         Make clear you're just stress-testing the thesis, not
-        obstructing, because the goal of the objective is a better final
-        decision, not winning.
+        obstructing, because the goal is a better final decision, not
+        winning.
 
     -   **Know When to Yield**:
         Conceding when the argument holds is what makes the challenge