@rse/ase 0.0.60 → 0.0.62

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

@@ -0,0 +1,301 @@
+---
+name: ase-meta-diff
+argument-hint: "[--help|-h] [--risk|-r] [--blast|-b]"
+description: >
+    Summarize the currently staged Git changes as a human-readable,
+    intent-grouped narrative. Use when the user wants a concise and
+    brief report of what changed and why. Optionally can show a risk and
+    blast radius report.
+user-invocable: true
+disable-model-invocation: false
+effort: high
+allowed-tools:
+    - "Bash(git diff *)"
+    - "Bash(git grep:*)"
+    - "Bash(git ls-files:*)"
+    - "Bash(grep:*)"
+    - "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-meta-diff">
+Summarize Diff
+</skill>
+
+<expand name="getopt"
+    arg1="ase-meta-diff"
+    arg2="--risk|-r --blast|-b">
+    $ARGUMENTS
+</expand>
+
+<objective>
+Summarize the currently staged Git changes into a *concise*,
+*human-readable* narrative of what changed and why, *grouped by
+intent* rather than by file. Optionally *score* the diff against a
+*coupling-criticality-coverage- reversibility* rubric and emit a *graded
+risk report* with *mitigations*. Optionally render a *blast-radius map*.
+</objective>
+
+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/>!
+
+<flow>
+
+1.  <step id="STEP 1: Determine Change Set">
+
+    1.  Determine the *diff details* by running the corresponding command
+        (taken exactly as given) and capturing the full diff output into
+        <diff/> for the subsequent analysis:
+
+        `git diff --cached HEAD`
+
+    2.  Determine the *diff statistics* by running the corresponding command
+        (taken exactly as given) and capturing the full stat output into
+        <stat/> for the subsequent analysis:
+
+        `git diff --cached --numstat HEAD`
+
+    </step>
+
+2.  <step id="STEP 2: Summarize By Intent">
+
+    1.  <if condition="<diff/> is empty">
+        Only output the following <template/> and then *STOP* immediately:
+
+        <template>
+        ⧉ **ASE**: ✪ skill: **ase-meta-diff**, ▶ status: **no changes to summarize**
+        </template>
+        </if>
+
+    2.   Analyze the <diff/> and <stat/> and synthesize a *concise* narrative of
+         WHAT changed and WHY, *grouped by intent* rather than by file.
+         Honor the following intents:
+
+         -   `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
+
+    3.  <if condition="<diff/> is NOT empty">
+        1.  First, output the following header <template/>:
+
+            <template>
+
+            <ase-tpl-bullet-normal/> **CHANGE INTENT REPORT**:
+
+            </template>
+
+        2.  Render a *two-column table* with one row per discovered
+            *intent group* present in the <diff/>. Output the following
+            table header <template/>:
+
+            <template>
+            | Intent | Changes (LoC) | Files &amp; Description |
+            | ------ | ------------- | ----------------------- |
+            </template>
+
+        3.  For each discovered *intent group*, emit the following row
+            <template/>, where <intent/> is the intent label, <changes/>
+            is the total number of lines changes per feature in format
+            `+N/-M`, <files/> is the list of affected file references,
+            and <description/> is a *brief* one-to-two-sentence
+            narrative of what changed and why:
+
+            <template>
+            | **<intent/>** | <changes/> | <files/>: <description/> |
+            </template>
+
+            In the <files/> part of the second column, markup all file
+            references as code (with backticks), prepend them with `▢ `,
+            append ` [+N/-M]` (based on the information in <stat/>) to them,
+            and separate them with `, ` (a comma and space). Do *not* repeat
+            file references in the <description/>.
+
+            Keep the overall report *concise* and *brief*. Try to keep the
+            number of intent groups (table rows) in the range of 1-10. Do
+            *not* output any further explanation.
+        </if>
+
+    </step>
+
+3.  <step id="STEP 3: Score Against Risk Rubric (optional)">
+
+    1.  <if condition="<getopt-option-risk/> is NOT equal `true`">
+        Silently *SKIP* this entire step.
+        </if>
+
+    2.  <if condition="<diff/> is empty">
+        Silently *SKIP* this entire step (STEP 2 already reported it).
+        </if>
+
+    3.  <if condition="<getopt-option-risk/> is equal `true` and <diff/> is NOT empty">
+
+        Score the *same* captured <diff/> and <stat/> information
+        against the four-axis rubric below. Each axis is scored on an
+        integer scale of *1* (lowest risk) to *5* (highest risk) against
+        the *fixed anchors* given, and *every* score *MUST* be backed
+        by a one-line <evidence/> grounded in the *actual* hunks or the
+        read-only repository probe.
+
+        Probe the repository *read-only* and *heuristically* (via `git
+        grep` / `grep` / `git ls-files`, restricted to first-party code)
+        only as needed to substantiate the *Coupling* and *Coverage*
+        axes (e.g. who imports a touched module, whether touched code has
+        adjacent tests). Do not output anything during the probe.
+
+        Score each axis against these anchors:
+
+        1.  **COUPLING** — how widely the touched code is depended upon.
+            *1*: self-contained, no first-party importers.
+            *3*: a handful of dependent modules.
+            *5*: a hub touched by many modules or a public interface.
+
+        2.  **CRITICALITY** — how essential the touched path is.
+            *1*: docs, comments, dead/peripheral code.
+            *3*: ordinary feature logic.
+            *5*: core/security/auth/data-integrity/money path.
+
+        3.  **COVERAGE** — how well the change is exercised by tests.
+            *1*: tests touched in this diff or directly covering the
+            changed hunks.
+            *3*: adjacent tests exist but are not clearly exercising the
+            changed hunks.
+            *5*: no tests anywhere near the touched code.
+
+        4.  **REVERSIBILITY** — how easily the change can be undone.
+            *1*: pure code change, revert restores prior state.
+            *3*: needs coordinated revert or a config rollback.
+            *5*: irreversible-by-revert (schema/data migration, released
+            artifact, external side effect).
+
+        Compute the *aggregate risk* as the *equal-weighted* mean of
+        the four risk contributions (Coupling, Criticality, Coverage,
+        Reversibility), rounded to one decimal, and map it to a *graded
+        band*: *1.0-1.9* → **LOW**, *2.0-2.9* → **MODERATE**, *3.0-3.9*
+        → **HIGH**, *4.0-5.0* → **CRITICAL**.
+
+        Then emit the following <template/>, with the overall band and
+        aggregate score, followed by a *three-column table* with one row
+        per axis: column 1 is the *axis*, column 2 is the *score*, and
+        column 3 is the *evidence* (as a `●` bullet point) plus —
+        *only* if the axis reached the mitigation threshold of '>= 4' —
+        the *mitigation* (as a second `●` bullet point). If an axis did
+        not reach that threshold, omit the ` ● **MITIGATION**:
+        <mitigation/>` part from its row. Keep the overall <evidence/>
+        and <mitigation/> texts *concise* and *ultra brief*. Do *not*
+        output any further explanation.
+
+        In <evidence/> markup all file references as code (with
+        backticks), prepend them with `▢ ` and append ` [+N/-M]` (based
+        on the information in <stat/>) to them.
+
+        <template>
+
+        <ase-tpl-bullet-signal/> **CHANGE RISK REPORT**: Overall: **<band/>** (<aggregate/>/5)
+
+        | Axis | Score | Findings |
+        | ---- | ----- | -------- |
+        </template>
+
+        For each axis, emit the following row <template/>:
+
+        <template>
+        | **<axis/>** | <score/>/5 | ● **EVIDENCE**: <evidence/> ● **MITIGATION**: <mitigation/> |
+        </template>
+
+        Finally, output the following footer <template/>:
+
+        <template>
+
+        </template>
+
+        </if>
+
+    </step>
+
+4.  <step id="STEP 4: Render Blast-Radius Map (optional)">
+
+    1.  <if condition="<getopt-option-blast/> is NOT equal `true`">
+        Silently *SKIP* this entire step.
+        </if>
+
+    2.  <if condition="<diff/> is empty">
+        Silently *SKIP* this entire step (STEP 2 already reported it).
+        </if>
+
+    3.  <if condition="<getopt-option-blast/> is equal `true` and <diff/> is NOT empty">
+        From the *same* captured <diff/> and <stat/>, *extract the
+        touched modules* — the distinct changed source files (or their
+        enclosing modules/ packages, according to the language idiom).
+
+        Then, for each touched module, *scan its reverse dependencies*
+        — the other first-party files that *import* or *reference* it
+        across the current project (e.g. by the module's basename,
+        exported symbol, or import path). Keep the scan *read-only*
+        and *heuristic*; restrict it to first-party code within the
+        repository. Do not output anything during the scan.
+
+        Then build a *blast-radius graph* and render it as a diagram:
+
+        1.  Build a Mermaid specification <mermaid-spec/> for a `flowchart
+            TB` whose *touched* modules are the origin nodes and whose
+            *reverse-dependency* edges fan out to the dependent modules
+            (origin → dependent).
+
+            Flag each *touched* node as a problem node per the
+            `ase-meta-diagram` anomaly convention — prefix its label
+            with `⚑ ` inside quotes, e.g. `T1["⚑ src/core.ts"]`. Keep
+            labels ultra short (basenames or module names only).
+
+        2.  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:ase-meta-diagram", prompt: "<mermaid-spec/>")` and capture
+            its returned `text` field as <diagram/>.
+
+        Then emit the following <template/>, showing <diagram/> and
+        appending a *brief impact summary* of bullets, where each
+        <module/> is a *touched* module and <impact/> is a one-sentence
+        note on *what depends on it* and *how far the blast reaches*.
+
+        In <module/> and <impact/>, markup all file references as code
+        (with backticks), prepend them with `▢ ` and append ` [+N/-M]`
+        (based on the information in <stat/>) to them.
+
+        <template>
+        <ase-tpl-head title="Hello World"/>
+
+        <ase-tpl-bullet-signal/> **CHANGE BLAST RADIUS MAP**:
+
+        ```text
+        <diagram/>
+        ```
+
+        <ase-tpl-bullet-signal/> **BLAST**: ⚑ **<module/>**: <impact/>
+
+        <ase-tpl-bullet-signal/> **BLAST**: ⚑ **<module/>**: <impact/>
+
+        [...]
+
+        <ase-tpl-foot/>
+        </template>
+
+        Keep the overall report *concise* and *brief*. Do *not* output
+        any further explanation.
+        </if>
+
+    </step>
+
+</flow>
+

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

@@ -0,0 +1,81 @@
+
+##  NAME
+
+`ase-meta-diff` - Summarize Diff
+
+##  SYNOPSIS
+
+`ase-meta-diff`
+    [`--help`|`-h`]
+    [`--risk`|`-r`]
+    [`--blast`|`-b`]
+
+##  DESCRIPTION
+
+The `ase-meta-diff` skill turns a raw Git diff into a *concise*,
+*human-readable* narrative of what changed and why, *grouped by
+intent* (such as *Feature*, *Improvement*, *Bugfix*, *Update*,
+*Cleanup*, or *Refactor*) rather than by file. It inspects the
+*staged* changes (`git diff --cached HEAD`). The result is a short
+bullet list, one bullet per intent group, each naming the affected
+files with their per-file `[+N/-M]` line counts — giving you the
+essence of the changes at a glance.
+
+With `--risk`, the skill additionally *scores* the same diff against a
+four-axis **coupling-criticality-coverage-reversibility** rubric and
+emits a *graded risk report* — one bullet per axis (each scored *1*-*5*
+with a one-line evidence justification drawn from the actual hunks), an
+overall risk band (**LOW**, **MODERATE**, **HIGH**, or **CRITICAL**),
+and one actionable *mitigation* per high-risk axis. The axes combine
+with *equal weights*, and the rubric is deliberately *not tuned* to any
+specific project: every score is backed by cited evidence so it remains
+*overridable*, and the report is *decision support*, not a merge gate.
+
+With `--blast`, the skill additionally renders a *blast-radius map* — a
+Mermaid `flowchart` of the *touched modules* and their *reverse
+dependencies*, plus a *brief impact summary*. It *extracts the touched
+modules* from the changed files, *scans the repository* for the
+first-party code that *imports* or *references* those modules, builds a
+blast-radius graph (touched modules as origin nodes, dependents fanning
+out along the edges), dispatches the rendering to the `ase-meta-diagram`
+sub-agent, and appends a short bullet list of the per-module impact —
+giving a visual sense of *what a diff endangers* before a deeper review.
+
+##  ARGUMENTS
+
+`--risk`, `-r`:
+    In addition to the intent-grouped summary, score the diff against
+    the *coupling-criticality-coverage-reversibility* rubric and emit a
+    *graded risk report* with an overall risk band and per-axis
+    *mitigations*. Scores are equal-weighted, evidence-backed, and
+    deliberately untuned to the project.
+
+`--blast`, `-b`:
+    In addition to the intent-grouped summary, render a *blast-radius
+    map* — a Mermaid `flowchart` of the *touched modules* and their
+    *reverse dependencies* — plus a *brief impact summary* of what
+    depends on the touched code and how far the blast reaches.
+
+##  EXAMPLES
+
+Summarize the currently staged changes:
+
+```text
+❯ /ase-meta-diff
+```
+
+Summarize the staged changes and append a graded risk report:
+
+```text
+❯ /ase-meta-diff --risk
+```
+
+Summarize the staged changes and append a blast-radius map:
+
+```text
+❯ /ase-meta-diff --blast
+```
+
+##  SEE ALSO
+
+`ase-meta-commit`, `ase-meta-changelog`, `ase-arch-analyze`.

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

@@ -33,7 +33,7 @@ multi-*criteria* decision matrix.
         and do not output anything else:
 
         <template>
-        &#x26AA; **REASON**: *<reason/>*
+        <ase-tpl-bullet-secondary/> **REASON**: *<reason/>*
         </template>
     </step>
 
@@ -47,7 +47,7 @@ multi-*criteria* decision matrix.
         executing any further steps:
 
         <template>
-        &#x1F7E0; **ERROR: INSUFFICIENT ALTERNATIVES**: at least two are required for a comparison!
+        <ase-tpl-bullet-signal/> **ERROR: INSUFFICIENT ALTERNATIVES**: at least two are required for a comparison!
         </template>
 
     -   For each alternative <alternative-K/> (K=1-N), decide whether
@@ -82,7 +82,7 @@ multi-*criteria* decision matrix.
         executing any further steps:
 
         <template>
-        &#x1F7E0; **ERROR: INCOMPARABLE ALTERNATIVES**: *<class-of-alternatives/>*
+        <ase-tpl-bullet-signal/> **ERROR: INCOMPARABLE ALTERNATIVES**: *<class-of-alternatives/>*
 
         <for items="<alternative-J/> [...]">
         ⚑ **<item/>** (*member of a different class*)
@@ -94,7 +94,7 @@ multi-*criteria* decision matrix.
         anything else:
 
         <template>
-        &#x1F535; **ALTERNATIVES**: *<class-of-alternatives/>*
+        <ase-tpl-bullet-normal/> **ALTERNATIVES**: *<class-of-alternatives/>*
 
         | ⚑ *Alternative*        | ⚖ *Hint*  |
         | :--------------------- | :-------- |
@@ -161,7 +161,7 @@ multi-*criteria* decision matrix.
         alternative* <alternative-K/> (K=1-N).
 
         <template>
-        &#x1F535; **EVALUATION**: *Weighted Multi-Criteria Decision Matrix*
+        <ase-tpl-bullet-normal/> **EVALUATION**: *Weighted Multi-Criteria Decision Matrix*
 
         | ⦿ *Criteria*  | ⚖ *Weight*  | ⚑ **<alternative-1/>** | [...alternatives 2-(N-1)...] | ⚑ **<alternative-N/>** |
         | :------------ | ----------: | ---------------------: | ---------------------------: | ---------------------: |
@@ -217,7 +217,7 @@ multi-*criteria* decision matrix.
         else:
 
         <template>
-        &#x1F7E0; **ERROR**: ✘ *MULTIPLE BEST ALTERNATIVES FOUND*,
+        <ase-tpl-bullet-signal/> **ERROR**: ✘ *MULTIPLE BEST ALTERNATIVES FOUND*,
         ⚠ *Please give some hints on the criteria to ensure a single best alternative!*
         </template>
 
@@ -226,7 +226,7 @@ multi-*criteria* decision matrix.
         else:
 
         <template>
-        &#x1F7E0; **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
+        <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
         ⚠ *ATTENTION: small distance to second best alternative!*
         </template>
 
@@ -236,7 +236,7 @@ multi-*criteria* decision matrix.
         output anything else:
 
         <template>
-        &#x1F7E0; **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
+        <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
         ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
         </template>
 
@@ -244,7 +244,7 @@ multi-*criteria* decision matrix.
         just the following <template/> and do not output anything else:
 
         <template>
-        &#x1F7E0; **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
+        <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
         </template>
     </step>
 </flow>

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

@@ -31,7 +31,7 @@ addressing surface-level symptoms.
     State the problem statement.
 
     <template>
-    &#x1F7E0; **PROBLEM**: <problem/>
+    <ase-tpl-bullet-signal/> **PROBLEM**: <problem/>
     </template>
     </step>
 
@@ -46,7 +46,7 @@ addressing surface-level symptoms.
         Consider technical, domain-specific, process-related, or organizational causes.
 
         <template>
-        &#x26AA; **WHY <item/>**: <answer/>
+        <ase-tpl-bullet-secondary/> **WHY <item/>**: <answer/>
         </template>
 
         Then, for the next iteration set <question/> now to be the last <answer/>.
@@ -61,7 +61,7 @@ addressing surface-level symptoms.
     For the proposed solution, optionally directly propose corresponding source code changes.
 
     <template>
-    &#x1F7E0; **SOLUTION**: <solution/>
+    <ase-tpl-bullet-signal/> **SOLUTION**: <solution/>
     </template>
     </step>
 </flow>

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

@@ -326,9 +326,9 @@ Set <content-dirty>true</content-dirty>.
         Use the following <template/>:
 
         <template>
-        ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
+        <ase-tpl-head title="TASK-PLAN"/>
         <content/>
-        ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(**  `TASK-PLAN-END`  **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
+        <ase-tpl-foot title="TASK-PLAN"/>
         </template>
 
     4.  *Determine next step*:

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

@@ -143,7 +143,7 @@ Procedure
         1.  Output the following <template/>:
 
             <template>
-            &#x1F7E0; ASPECT <N/>/<n/>: **<aspect-N/>**, QUESTION: **<question-N/>**
+            <ase-tpl-bullet-signal/> ASPECT <N/>/<n/>: **<aspect-N/>**, QUESTION: **<question-N/>**
             </template>
 
         2.  Determine the answer alternatives:
@@ -164,7 +164,7 @@ Procedure
             4.  Output the following <template/>:
 
                 <template>
-                &#x1F535; ASPECT <N/>/<n/>: **<aspect-N/>**, ANSWER: **<answer-N/>**
+                <ase-tpl-bullet-normal/> ASPECT <N/>/<n/>: **<aspect-N/>**, ANSWER: **<answer-N/>**
                 </template>
 
     3.  Finally, update the in <plan/> based on all answers <answer-N/>.

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

@@ -82,9 +82,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
         <content/> here.
 
         <template>
-        ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
+        <ase-tpl-head title="TASK-PLAN"/>
         <content/>
-        ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(**  `TASK-PLAN-END`  **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
+        <ase-tpl-foot title="TASK-PLAN"/>
         </template>
         </if>