@rse/ase 2.0.2 → 2.0.4

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-lint
-argument-hint: "[--help|-h] [--auto|-a] [--severity|-S=(LOW|MEDIUM|HIGH)] [--include|-i=<aspect>[,...]] [--exclude|-e=<aspect>[,...]] [--staged] [--unstaged] [<source-reference>]"
+argument-hint: "[--help|-h] [--auto|-a] [--severity|-S=(AUTO|LOW|MEDIUM|HIGH)] [--include|-i=<aspect>[,...]] [--exclude|-e=<aspect>[,...]] [--staged] [--unstaged] [<source-reference>]"
 description: >
     Lint source code for potential code quality problems.
     Use when the user wants to "lint" or "check" source code.
@@ -23,7 +23,7 @@ Lint Source Code
 
 <expand name="getopt"
     arg1="ase-code-lint"
-    arg2="--auto|-a --severity|-S=(LOW|MEDIUM|HIGH) --include|-i=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --exclude|-e=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --staged --unstaged">
+    arg2="--auto|-a --severity|-S=(AUTO|LOW|MEDIUM|HIGH) --include|-i=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --exclude|-e=(none|A01|A02|A03|A04|A05|A06|A07|A08|A09|A10|A11|A12|A13|A14|A15|A16|A17|A18|A19|A20|A21)... --staged --unstaged">
     $ARGUMENTS
 </expand>
 
@@ -36,10 +36,11 @@ related to a set of code quality aspects.
 
 1.  <step id="STEP 1: Investigation">
 
-    <if condition="<ase-project-boxing/> is equal `black`">
+    <if condition="<ase-project-boxing/> is equal `black` and <getopt-option-severity/> is equal `AUTO`">
 
     The project source artifacts are classified as a *black box*, so
-    the user does *not* want them inspected or their problems surfaced.
+    the user does *not* want them inspected or their problems surfaced
+    (an *explicitly* given severity floor lifts this skip).
     *Skip* the entire investigation and reporting: do *not* invoke any
     `Bash`, `Glob`, or `Agent` tool and do *not* read any source, only
     output the following <template/> and then *SKIP* the remaining steps
@@ -51,6 +52,11 @@ related to a set of code quality aspects.
 
     </if>
 
+    Set <condensed>true</condensed> if <ase-project-boxing/> is equal
+    `grey` or `black` (the latter reached only under an explicitly given
+    severity floor), and <condensed>false</condensed> otherwise: a
+    *condensed* report suppresses the full unified diffs of STEP 3.
+
     First, determine the *effective aspect set* <aspects/>, i.e., the
     code quality aspects which are checked at all. For this, parse
     <getopt-option-include/> and <getopt-option-exclude/> as
@@ -179,16 +185,23 @@ related to a set of code quality aspects.
     `line`, and set <problems/> to that list.
 
     Then determine the *effective severity floor* <floor/>: define the
-    ordinal rank `LOW`=1, `MEDIUM`=2, `HIGH`=3, start from
-    <floor><getopt-option-severity/></floor> (default `LOW`), and - if
-    <ase-project-boxing/> is equal `grey` - raise <floor/> to `MEDIUM`
-    whenever its current rank is below `rank(MEDIUM)` (grey boxing
-    surfaces only *material* findings of severity `MEDIUM` and above).
+    ordinal rank `LOW`=1, `MEDIUM`=2, `HIGH`=3.
+
+    <if condition="<getopt-option-severity/> is equal `AUTO`">
+    Set <floor>MEDIUM</floor> if <ase-project-boxing/> is equal `grey`
+    (grey boxing surfaces only *material* findings of severity `MEDIUM`
+    and above), and <floor>LOW</floor> otherwise.
+    </if>
+    <else>
+    Set <floor><getopt-option-severity/></floor>: an *explicitly* given
+    severity floor always *wins* over the boxing, both over the `grey`
+    floor and over the `black` skip.
+    </else>
 
     Then *apply the effective severity floor* <floor/>: *Keep* a problem
     in <problems/> if and only if its `severity` field is `ACCEPTED` *or*
     `rank(severity)` is greater than or equal to `rank(<floor/>)`;
-    *silently drop* all other problems. With the default floor `LOW`, all
+    *silently drop* all other problems. With the floor `LOW`, all
     problems are kept. `ACCEPTED` problems are *never* dropped.
 
     Finally, sort the surviving problems in <problems/> by their
@@ -270,7 +283,7 @@ related to a set of code quality aspects.
             1.  Set <file/>         to the `file`         field of <item/>.
                 Set <change-hunks/> to the `change-hunks` field of <item/>.
 
-                Unless <ase-project-boxing/> is equal `grey` (where the
+                Unless <condensed/> is equal `true` (where the
                 full unified diff is suppressed and no context lines are
                 rendered at all), *silently* read the current content of
                 <file/> with the `Read` tool - reusing the content read
@@ -284,7 +297,7 @@ related to a set of code quality aspects.
                 context lines of substep 2 below, so the rendered diff
                 shows real context even when a sub-agent supplied none.
 
-                Unless <ase-project-boxing/> is equal `grey` (where the
+                Unless <condensed/> is equal `true` (where the
                 full unified diff is suppressed and this per-file header is
                 unused), set <diff-file/> to the following <template/>:
 
@@ -328,8 +341,8 @@ related to a set of code quality aspects.
                     Keep the sub-agent supplied values only when
                     <file-lines/> is empty.
 
-                2.  *Skip* this substep entirely when <ase-project-boxing/>
-                    is equal `grey` - the full unified diff is suppressed
+                2.  *Skip* this substep entirely when <condensed/>
+                    is equal `true` - the full unified diff is suppressed
                     there, so none of the <hunk-body/>, <old-count/>,
                     <new-count/>, <old-start/>, or <new-start/> values
                     below are consumed (substep 4 builds only the condensed
@@ -384,10 +397,10 @@ related to a set of code quality aspects.
 
                     <template>`<file/>`:<line/></template>
 
-                4.  <if condition="<ase-project-boxing/> is equal `grey`">
+                4.  <if condition="<condensed/> is equal `true`">
 
-                    The full unified diff is *suppressed* under grey boxing
-                    (see substep 5 below), so *skip* the full-diff append
+                    The full unified diff is *suppressed* in a condensed
+                    report (see substep 5 below), so *skip* the full-diff append
                     and instead build only a *condensed* one-line
                     representation of this hunk: determine <old-snippet/>
                     as the *single-line* collapse of <old-text/> (join its
@@ -417,7 +430,7 @@ related to a set of code quality aspects.
 
                 </for>
 
-            3.  Unless <ase-project-boxing/> is equal `grey` (where
+            3.  Unless <condensed/> is equal `true` (where
                 <diff-file/> is unused), append <diff-file/> to <diff/>.
 
             </for>
@@ -433,10 +446,11 @@ related to a set of code quality aspects.
 
         5.  <if condition="<getopt-option-auto/> is not equal `true`">
 
-            <if condition="<ase-project-boxing/> is equal `grey`">
+            <if condition="<condensed/> is equal `true`">
 
-            The project source artifacts are classified as a *grey box*, so
-            the user does *not* want the full artifact internals surfaced:
+            The project source artifacts are classified as a *grey box* (or
+            *black box*), so the user does *not* want the full artifact
+            internals surfaced:
             *suppress* the full unified diff and instead show only the
             *condensed* one-line-per-hunk representation. Report the
             solution with the following <template/>:
@@ -505,8 +519,8 @@ related to a set of code quality aspects.
             -   <if condition="<result/> is 'ACCEPT'">
                 Invoke the `Edit` tool to apply the changes exactly
                 as given by the hunks of the current <change-set/>
-                (rendered as <diff/>, unless suppressed under grey
-                boxing). The operation will be auto-approved by the ASE
+                (rendered as <diff/>, unless suppressed in a condensed
+                report). The operation will be auto-approved by the ASE
                 `pre-tool-use` hook (which tracks the active skill),
                 so *no* interactive permission prompt will appear.
                 After applying the changes, just continue with the next

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

@@ -8,7 +8,7 @@
 `ase-code-lint`
     [`--help`|`-h`]
     [`--auto`|`-a`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--include`|`-i`=*aspect*[`,`...]]
     [`--exclude`|`-e`=*aspect*[`,`...]]
     [`--staged`]
@@ -60,11 +60,16 @@ the code, and comments contradicting the code.
     Automatically apply every proposed correction without asking the
     user via the interactive dialog.
 
--   `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
-    Set the *severity floor* (default `LOW`): findings below the chosen
+-   `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`):
+    Set the *severity floor* (default `AUTO`): findings below the chosen
     threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
-    `HIGH`. The default `LOW` keeps all findings; `ACCEPTED` findings are
-    never suppressed. Surviving findings are reported in *descending
+    `HIGH`. The default `AUTO` means `MEDIUM` for a project with `grey`
+    boxing, no linting at all for a project with `black` boxing, and
+    `LOW` (keep all findings) otherwise; an explicitly given floor always
+    wins over the boxing, i.e. it also lints a project with `black`
+    boxing and, e.g. with `LOW`, acts on all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed. Surviving
+    findings are reported in *descending
     severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED`, keeping the
     `file`/`line` order within the same severity.
 

package/plugin/skills/ase-help-intent/data.md

@@ -175,7 +175,7 @@ Discover HTTP clients, flagging any without a release in the last 12 months:
     [`--help`|`-h`]
     [`--performance`|`-p`]
     [`--security`|`-s`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--prefix`|`-P` *prefix*]
     [`--staged`]
     [`--unstaged`]
@@ -198,11 +198,16 @@ The *analysis lens* depends on the selected options:
 
 The `--performance` and `--security` options are *mutually exclusive*.
 
-The `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`) option sets a *severity
-floor* (default `LOW`): problems below the chosen threshold are silently
-suppressed (neither reported nor persisted), ordered `LOW` < `MEDIUM` <
-`HIGH`. The default `LOW` keeps all problems; `ACCEPTED` problems are
-never suppressed. Surviving problems are reported in *descending
+The `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`) option sets a
+*severity floor* (default `AUTO`): problems below the chosen threshold
+are silently suppressed (neither reported nor persisted), ordered `LOW`
+< `MEDIUM` < `HIGH`. The default `AUTO` means `MEDIUM` for a project
+with `grey` boxing, no analysis at all for a project with `black`
+boxing, and `LOW` (keep all problems) otherwise; an explicitly given
+floor always wins over the boxing, i.e. it also analyzes a project with
+`black` boxing and, e.g. with `LOW`, reports all problems of a project
+with `grey` boxing. `ACCEPTED` problems are never suppressed. Surviving
+problems are reported in *descending
 severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED` - keeping the
 `file`/`line` order within the same severity - and are renumbered
 contiguously as `P<n>`, so `P1` is the most severe problem.
@@ -627,7 +632,7 @@ Get insights into a specific subsystem:
 `ase-code-lint`
     [`--help`|`-h`]
     [`--auto`|`-a`]
-    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
     [`--include`|`-i`=*aspect*[`,`...]]
     [`--exclude`|`-e`=*aspect*[`,`...]]
     [`--staged`]
@@ -679,11 +684,16 @@ the code, and comments contradicting the code.
     Automatically apply every proposed correction without asking the
     user via the interactive dialog.
 
--   `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
-    Set the *severity floor* (default `LOW`): findings below the chosen
+-   `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`):
+    Set the *severity floor* (default `AUTO`): findings below the chosen
     threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
-    `HIGH`. The default `LOW` keeps all findings; `ACCEPTED` findings are
-    never suppressed. Surviving findings are reported in *descending
+    `HIGH`. The default `AUTO` means `MEDIUM` for a project with `grey`
+    boxing, no linting at all for a project with `black` boxing, and
+    `LOW` (keep all findings) otherwise; an explicitly given floor always
+    wins over the boxing, i.e. it also lints a project with `black`
+    boxing and, e.g. with `LOW`, acts on all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed. Surviving
+    findings are reported in *descending
     severity* order `HIGH`, `MEDIUM`, `LOW`, `ACCEPTED`, keeping the
     `file`/`line` order within the same severity.
 
@@ -3170,7 +3180,9 @@ before it is committed or merged.
     threshold are suppressed, ordered `LOW` < `MEDIUM` < `HIGH`. The
     default `AUTO` means `MEDIUM` for a project with `grey` boxing and
     `LOW` (keep all findings) otherwise; an explicitly given floor always
-    wins over the boxing. `ACCEPTED` findings are never suppressed, and
+    wins over the boxing, i.e. it also reviews a project with `black`
+    boxing and, e.g. with `LOW`, shows all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed, and
     the number of suppressed findings is always reported. Surviving
     findings are rendered in *descending severity* order `HIGH`,
     `MEDIUM`, `LOW`, `ACCEPTED`. The floor only affects the rendered
@@ -3562,6 +3574,175 @@ Loop over multiple specification edits inside a dedicated Git worktree:
 ❯ /ase-spec-edit -l -w event-series
 ```
 
+</purpose>
+<purpose name="ase-spec-lint">
+
+##  NAME
+
+`ase-spec-lint` - Lint Specification
+
+##  SYNOPSIS
+
+`ase-spec-lint`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    [`--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`)]
+    [`--include`|`-i`=*aspect*[`,`...]]
+    [`--exclude`|`-e`=*aspect*[`,`...]]
+    [`--staged`]
+    [`--unstaged`]
+    [*spec-reference*]
+
+##  DESCRIPTION
+
+The `ase-spec-lint` skill lints the *SpecBook*-based specification
+(SPEC) for *potential quality problems* related to a fixed set of
+specification quality aspects: from its syntax and formatting, over
+its individual statements, up to the logical gaps of its model and its
+completeness for an implementation. The investigation is dispatched to
+sub-agents (`ase:ase-spec-lint`) so that scanning details do not leak
+into the user-visible transcript.
+
+For each detected problem, the skill renders a unified-diff *SOLUTION*
+preview and either asks the user to `ACCEPT` or `REJECT` the proposed
+correction interactively (or refine it via a free-text hint, which
+re-proposes the correction without limit) or - with `--auto` - applies
+all corrections automatically. Every applied correction refreshes the
+`Modified:` timestamp of the changed specification files.
+
+By default all ten specification quality aspects are checked. The
+`--include` and `--exclude` options narrow this to an *effective aspect
+set*: with `--include` only, exactly the listed aspects are checked;
+with `--exclude` only, all aspects except the listed ones; with both,
+the included ones minus the excluded ones. An unknown aspect id, or a
+combination which cancels out to an empty set, aborts the skill with an
+error. The ten aspect ids are:
+
+```text
+S01 SYNTAX      S04 AMBIGUITY     S07 REDUNDANCY    S10 COMPLETENESS
+S02 FORMAT      S05 ATOMICITY     S08 CONSISTENCY
+S03 RATIONALE   S06 REALIZATION   S09 LOGIC
+```
+
+The `S01 SYNTAX` aspect reports the diagnostics of the specification
+linting against the *SpecBook* schema configuration of the project and
+of the generic Markdown linting via *markdownlint* (both as with `ase
+spec lint --markdown`), mapping the severity `error` onto `HIGH` and
+`warning` onto `MEDIUM`. The `S02 FORMAT` aspect checks the formatting
+against the *SpecBook* format variants and the prevailing conventions
+of the specification itself. The aspects `S03 RATIONALE` up to `S07
+REDUNDANCY` check the statements against the *Specifying Tenets* of
+*ASE*: a `, BECAUSE` rationale per statement, unambiguous and
+verifiable statements, atomic statements, intent instead of
+realization, and a single source of truth per fact.
+
+The *model-wide* aspects `S07 REDUNDANCY` up to `S10 COMPLETENESS` are
+judged on the *entire* specification, even if only parts of it are
+linted: `S08 CONSISTENCY` checks for contradictions and drifting
+terminology, `S09 LOGIC` for logical gaps in the specification model
+(like unreachable states or entities without any relationship), and
+`S10 COMPLETENESS` for open ends which would force an implementer to
+guess. As the corrections of `S09 LOGIC` and `S10 COMPLETENESS` fill
+gaps with *best-guess* content, they are proposed for review only and
+are *never* applied under `--auto`.
+
+##  OPTIONS
+
+-   `--auto`|`-a`:
+    Automatically apply every proposed correction without asking the
+    user via the interactive dialog, except for the best-guess
+    corrections of the aspects `S09 LOGIC` and `S10 COMPLETENESS`,
+    which are only reported.
+
+-   `--severity`|`-S`=(`AUTO`|`LOW`|`MEDIUM`|`HIGH`):
+    Set the *severity floor* (default `AUTO`): findings below the chosen
+    threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
+    `HIGH`. The default `AUTO` means `MEDIUM` for a project with `grey`
+    boxing, no linting at all for a project with `black` boxing, and
+    `LOW` (keep all findings) otherwise; an explicitly given floor always
+    wins over the boxing, i.e. it also lints a project with `black`
+    boxing and, e.g. with `LOW`, acts on all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed. Surviving
+    findings are reported in *descending severity* order `HIGH`,
+    `MEDIUM`, `LOW`, `ACCEPTED`, keeping the `file`/`line` order within
+    the same severity.
+
+-   `--include`|`-i`=*aspect*[`,`...]:
+    Restrict the checked specification quality aspects to the given
+    comma-separated list of aspect ids (e.g. `S01,S02`). Without this
+    option, all ten aspects are checked.
+
+-   `--exclude`|`-e`=*aspect*[`,`...]:
+    Remove the given comma-separated list of aspect ids from the checked
+    specification quality aspects. Applied *after* `--include`, so
+    `-i S09,S10 -e S10` checks `S09` only.
+
+-   `--staged`:
+    Restrict the linting to the specification files with *staged* Git
+    changes. Deleted files are skipped, and the files are linted in
+    their current working copy state. Combined with `--unstaged`, lint
+    the specification files with *any* uncommitted Git changes.
+
+-   `--unstaged`:
+    Restrict the linting to the specification files with *unstaged* Git
+    changes plus the *untracked* specification files. Deleted files are
+    skipped. Combined with `--staged`, lint the specification files with
+    *any* uncommitted Git changes.
+
+##  ARGUMENTS
+
+-   *spec-reference*:
+    A file, directory, or wildcard reference to the specification files
+    to lint. Without it, the *entire* specification is linted, resp.
+    under `--staged` or `--unstaged` all changed specification files.
+
+##  SCENARIOS
+
+-   You want your specification checked for specification quality problems
+-   You want to know whether your specification is sufficient for an implementation
+-   You want logical gaps in your specification model detected
+-   You want corrections proposed which you accept or reject one by one
+-   You want all mechanical corrections applied automatically
+-   You want only your staged or unstaged specification changes linted before committing
+
+##  EXAMPLES
+
+Lint the entire specification interactively:
+
+```text
+❯ /ase-spec-lint
+```
+
+Lint a single specification file and automatically apply all corrections:
+
+```text
+❯ /ase-spec-lint --auto docs/spec/data-model.md
+```
+
+Lint the specification for its syntax and formatting only:
+
+```text
+❯ /ase-spec-lint -i S01,S02
+```
+
+Check the specification model for logical gaps and completeness only:
+
+```text
+❯ /ase-spec-lint -i S09,S10
+```
+
+Lint the specification, reporting only `MEDIUM` and `HIGH` findings:
+
+```text
+❯ /ase-spec-lint -S MEDIUM
+```
+
+Lint only the specification files with staged Git changes:
+
+```text
+❯ /ase-spec-lint --staged
+```
+
 </purpose>
 <purpose name="ase-sync-export">
 
@@ -4835,6 +5016,7 @@ Switch to a specific task:
     [`--source`|`-s` *source*]
     [`--changeset`|`-c` *changeset*]
     [`--draft`|`-d`]
+    [`--no-cleanup`|`-K`]
     [`--stateless`|`-S`]
     [*id*]
 
@@ -4877,7 +5059,9 @@ overridable via `--changeset`:
 -   `branch:`*name*: the change set is *committed* onto the branch
     *name* -- created from the source if missing -- inside the worktree
     in which this branch is checked out, or inside a newly created
-    worktree `.ase/worktree/<name>`.
+    worktree `.ase/worktree/<name>`, which is removed again after the
+    commit (unless `--no-cleanup` is given), while an already existing
+    worktree is always kept.
 -   `attachment:`*name*: the change set is made and verified in a
     *temporary* worktree, detached at the source commit, and stored as
     the attachment block of type `text/x-diff; charset=utf-8;
@@ -4984,6 +5168,13 @@ plan, unless `--next` pre-selects this choice.
     *implementation draft* of the plan only, leaving all artifacts
     untouched (a dry-run). Mutually exclusive with `--changeset`.
 
+-   `--no-cleanup`|`-K`:
+    For a `branch:` changeset, keep the worktree `.ase/worktree/<name>`
+    newly created by this run, instead of removing it after the commit,
+    so the change set can be reviewed, built, and tested there. Without
+    this option, the worktree is removed only if it has no uncommitted
+    changes, as the change set lives on the branch alone.
+
 -   `--stateless`|`-S`:
     Leave the plan's `Status:` key untouched.
 

package/plugin/skills/ase-help-skill/catalog.md

@@ -23,6 +23,7 @@
 ⎈   **SPECIFICATION**
 ○   `ase-spec-activate`:   Activate Specification Know-How
 ○   `ase-spec-edit`:       Edit Specification
+○   `ase-spec-lint`:       Lint Specification
 
 ⎈   **CODING**
 ○   `ase-code-analyze`:    Analyze Source Code

package/plugin/skills/ase-meta-workflow/workflow.txt

@@ -15,6 +15,7 @@ START               -> ase-arch-discover
 START               -> ase-code-insight
 START               -> ase-code-explain
 START               -> ase-code-lint
+START               -> ase-spec-lint
 START               -> ase-docs-shorten
 START               -> ase-docs-refine
 START               -> ase-docs-proofread
@@ -46,6 +47,7 @@ ase-arch-discover   -> END
 ase-code-insight    -> END
 ase-code-explain    -> END
 ase-code-lint       -> END
+ase-spec-lint       -> END
 ase-docs-shorten    -> END
 ase-docs-refine     -> END
 ase-docs-proofread  -> END

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

@@ -71,6 +71,7 @@ currently staged Git changes.
     -   Use imperative mood ("add" not "added")
     -   Use *no* period at the end
     -   Use *no* Markdown formatting
+    -   Never add `Co-Authored-By` trailers to commit messages
 
     Output this crafted commit message with the following <template/>:
 

package/plugin/skills/ase-repo-merge/SKILL.md

@@ -121,6 +121,7 @@ processing the entire current skill:
         imperative-mood summary without a trailing period, without
         Markdown formatting, and without any double-quote (`"`),
         backtick (`` ` ``), dollar (`$`), or backslash (`\`) characters.
+        Never add `Co-Authored-By` trailers to commit messages.
 
     4.  Commit the changes by running the command
         `git -C "<source-dir/>" commit -m "<message/>"`. If it fails,

package/plugin/skills/ase-repo-review/SKILL.md

@@ -224,11 +224,12 @@ Procedure
 
 2.  <step id="STEP 2: Review Investigation">
 
-    <if condition="<ase-project-boxing/> is equal `black`">
+    <if condition="<ase-project-boxing/> is equal `black` and <getopt-option-severity/> is equal `AUTO`">
 
     The project source artifacts are classified as a *black box*, so
     the user does *not* want the changes scrutinized or their
-    findings surfaced. *Skip* the entire review investigation: do
+    findings surfaced (an *explicitly* given severity floor lifts this
+    skip). *Skip* the entire review investigation: do
     *not* invoke the `Agent` tool and do *not* read any change, set
     <findings/> to the *empty* list, set <hidden/> to `0`, set
     <verdict/> to `SKIPPED (boxing: black)`, set <summary/> to a
@@ -288,7 +289,8 @@ Procedure
     <else>
     Set <floor><getopt-option-severity/></floor> and
     <floor-origin>--severity <getopt-option-severity/></floor-origin>:
-    an *explicitly* given severity floor always *wins* over the boxing.
+    an *explicitly* given severity floor always *wins* over the boxing,
+    both over the `grey` floor and over the `black` skip.
     </else>
 
     Then *apply the effective severity floor* <floor/>: *Keep* a finding

package/plugin/skills/ase-repo-review/help.md

@@ -75,7 +75,9 @@ before it is committed or merged.
     threshold are suppressed, ordered `LOW` < `MEDIUM` < `HIGH`. The
     default `AUTO` means `MEDIUM` for a project with `grey` boxing and
     `LOW` (keep all findings) otherwise; an explicitly given floor always
-    wins over the boxing. `ACCEPTED` findings are never suppressed, and
+    wins over the boxing, i.e. it also reviews a project with `black`
+    boxing and, e.g. with `LOW`, shows all findings of a project with
+    `grey` boxing. `ACCEPTED` findings are never suppressed, and
     the number of suppressed findings is always reported. Surviving
     findings are rendered in *descending severity* order `HIGH`,
     `MEDIUM`, `LOW`, `ACCEPTED`. The floor only affects the rendered

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

@@ -393,9 +393,9 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
 
         <if condition="<worktree-dir/> is not empty">
         Run the command `ase spec lint` with <worktree-dir/> as its
-        working directory and parse its
-        `<file/>:<line/>:<column/>: <message/>` output lines into
-        <diagnostics/> -- the `ase_specbook_lint` tool always validates
+        working directory and parse its logged
+        `lint: specbook: <file/>:<line/>:<column/>: <message/>` lines
+        (on standard error) into <diagnostics/> -- the `ase_specbook_lint` tool always validates
         the *project* working copy and hence *MUST* *NOT* be used here.
         </if>
         <else>

package/plugin/skills/ase-spec-edit/help.md

@@ -215,5 +215,5 @@ Loop over multiple specification edits inside a dedicated Git worktree:
 
 ##  SEE ALSO
 
-[`ase-spec-activate`](../ase-spec-activate/help.md), [`ase-code-edit`](../ase-code-edit/help.md), [`ase-sync-import`](../ase-sync-import/help.md),
+[`ase-spec-activate`](../ase-spec-activate/help.md), [`ase-spec-lint`](../ase-spec-lint/help.md), [`ase-code-edit`](../ase-code-edit/help.md), [`ase-sync-import`](../ase-sync-import/help.md),
 [`ase-sync-reconcile`](../ase-sync-reconcile/help.md), [`ase-sync-export`](../ase-sync-export/help.md), [`ase-task-grill`](../ase-task-grill/help.md).