@rse/ase 0.0.55 → 0.0.57

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-explain
-argument-hint: "<source-reference>"
+argument-hint: "[--help|-h] <source-reference>"
 description: >
     Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS.
     Use when you want to know how code works or when the user asks "how does this work?"
@@ -15,18 +15,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Explain Source Code
-===================
-
 <skill name="ase-code-explain">
 Explain Source Code
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *explaining source code*.
-</role>
-
 <objective>
 *Analyze* the source code of $ARGUMENTS, and its directly related source
 code and *explain* it in a *brief*, *standardized*, and *concise* way.

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-code-explain` - Explain Source Code
+
+##  SYNOPSIS
+
+`ase-code-explain`
+    [`--help`|`-h`]
+    *source-reference*
+
+##  DESCRIPTION
+
+The `ase-code-explain` skill analyzes and explains the source code of
+the referenced location in a *brief*, *standardized*, and *concise*
+way along six dimensions: *WHAT* (functionality), *WHY* (rationale),
+*ANALOGY* (everyday-life comparison in ELI5 style), *DIAGRAM* (Mermaid
+diagram of control flow, data flow, or structure), *CRUXES* (what to
+notice), and *GOTCHAS* (what to not stumble over).
+
+##  ARGUMENTS
+
+*source-reference*:
+    A file, directory, function, or other reference to the source code
+    to explain.
+
+##  EXAMPLES
+
+Explain a single source file:
+
+```text
+❯ /ase-code-explain src/parser.ts
+```
+
+Explain a specific function:
+
+```text
+❯ /ase-code-explain src/parser.ts#parseExpression
+```
+
+##  SEE ALSO
+
+`ase-code-insight`, `ase-code-analyze`, `ase-arch-analyze`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-insight
-argument-hint: "<code-references>"
+argument-hint: "[--help|-h] <code-references>"
 description: >
     Give insights into the source code.
 user-invocable: true
@@ -18,18 +18,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Project Insight
-===============
-
 <skill name="ase-code-insight">
 Project Insight
 </skill>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *analyzing source code* and giving insights.
-</role>
-
 <objective>
 Give *insights* into the project through the source code of $ARGUMENTS.
 </objective>

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-code-insight` - Project Insight
+
+##  SYNOPSIS
+
+`ase-code-insight`
+    [`--help`|`-h`]
+    *code-references*
+
+##  DESCRIPTION
+
+The `ase-code-insight` skill gives high-level *insights* into the
+project through the referenced source code. The skill produces four
+sections: a *PROJECT ABSTRACT* (summary derived from `README.*` or
+source scanning), a *PROJECT AUTHOR* list (from `git shortlog`),
+a *SOURCE CHURN* table (most-committed files in the last year), and
+a *MODULE STRUCTURE* Mermaid diagram of modules and their imports.
+
+##  ARGUMENTS
+
+*code-references*:
+    One or more file or directory references to source code that
+    should be inspected for insights.
+
+##  EXAMPLES
+
+Get insights into the current project:
+
+```text
+❯ /ase-code-insight src/
+```
+
+Get insights into a specific subsystem:
+
+```text
+❯ /ase-code-insight tool/src/
+```
+
+##  SEE ALSO
+
+`ase-code-explain`, `ase-code-analyze`, `ase-arch-analyze`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-lint
-argument-hint: "<source-reference>"
+argument-hint: "[--help|-h] [--auto|-a] <source-reference>"
 description: >
     Lint source code for potential code quality problems.
     Use when the user wants to "lint" or "check" source code.
@@ -14,9 +14,6 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Lint Source Code
-================
-
 <skill name="ase-code-lint">
 Lint Source Code
 </skill>
@@ -27,11 +24,6 @@ Lint Source Code
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*,
-specialized in *analyzing source code*.
-</role>
-
 <objective>
 *Analyze* the code of `<getopt-arguments/>` for *potential problems*
 related to a set of code quality aspects.

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

@@ -0,0 +1,54 @@
+
+##  NAME
+
+`ase-code-lint` - Lint Source Code
+
+##  SYNOPSIS
+
+`ase-code-lint`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    *source-reference*
+
+##  DESCRIPTION
+
+The `ase-code-lint` skill lints the source code of the referenced
+location for *potential code quality problems* related to a fixed set
+of code quality aspects. The investigation is dispatched to a
+sub-agent (`ase:ase-code-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 — with `--auto` — applies all corrections
+automatically.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically apply every proposed correction without asking the
+    user via the interactive dialog.
+
+##  ARGUMENTS
+
+*source-reference*:
+    A file, directory, or other reference to the source code to lint.
+
+##  EXAMPLES
+
+Lint a source file interactively:
+
+```text
+❯ /ase-code-lint src/server.ts
+```
+
+Lint a directory and automatically apply all corrections:
+
+```text
+❯ /ase-code-lint --auto src/handlers/
+```
+
+##  SEE ALSO
+
+`ase-code-analyze`, `ase-code-resolve`, `ase-code-refactor`,
+`ase-docs-proofread`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-refactor
-argument-hint: "[<task-id>:] <request>"
+argument-hint: "[--help|-h] [--auto|-a] [--next|-n <option>] [<task-id>:] <request>"
 description: >
     Refactor Code Base:
     Use when user wants to refactor the code base.
@@ -17,9 +17,6 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Refactor Artifacts
-==================
-
 <skill name="ase-code-refactor">
 Refactor Artifacts
 </skill>
@@ -30,10 +27,6 @@ Refactor Artifacts
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*.
-</role>
-
 <objective>
 *Refactor* existing artifacts the following way:
 <request><getopt-arguments/></request>
@@ -61,7 +54,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ">
         Set <ase-task-id><request/></ase-task-id> (set task id to request)
         and <request></request> (set request empty), call the
-        `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
+        `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool
         from the `ase` MCP server to switch the task, and then only
         output the following <template/>:
 
@@ -73,8 +66,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  If <request/> has the format `<id/>: <text/>` where <id/> matches
         the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
         <request><text/></request> and <ase-task-id><id/></ase-task-id>
-        and call the `ase_task_id(id: <ase-task-id/>, session:
-        <ase-session-id/>)` tool from the `ase` MCP server to
+        and call the `ase_task_id(id: "<ase-task-id/>", session:
+        "<ase-session-id/>")` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
 
     3.  If <request/> is empty,
@@ -91,8 +84,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ">
         Set <ase-task-id/> to a unique task id, derived from <request/>,
         which consists of two lower-case words concatenated with a
-        `-` character. Then call the `ase_task_id(id: <ase-task-id/>,
-        session: <ase-session-id/>)` tool from the `ase` MCP server to
+        `-` character. Then call the `ase_task_id(id: "<ase-task-id/>",
+        session: "<ase-session-id/>")` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
         </if>
 
@@ -270,7 +263,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         words <words/> of <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: "<content/>")`.
 
     4.  Output a hint with the following <template/>:
 
@@ -278,9 +271,26 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    5.  Directly pass-through control to the `ase:ase-task-edit` skill.
-        Set <args></args> (set args to empty). If <getopt-option-next/>
-        is not equal `none`, set <args><args/> --next
-        <getopt-option-next/></args> (append to args). Then call the
-        tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+    5.  Directly pass-through control to the next skill:
+
+        1.  <if condition="<getopt-option-next/> is equal `IMPLEMENT`">
+            Call the tool `Skill(skill: "ase:ase-task-implement")` to
+            *implement* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        2.  <if condition="<getopt-option-next/> is equal `PREFLIGHT`">
+            Call the tool `Skill(skill: "ase:ase-task-preflight")` to
+            *preflight* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        3.  <if condition="
+                <getopt-option-next/> is not equal `IMPLEMENT` AND
+                <getopt-option-next/> is not equal `PREFLIGHT`
+            ">
+            Set <args></args> (set args to empty).
+            <if condition="<getopt-option-next/> is not equal `none`">
+            Set <args><args/> --next <getopt-option-next/></args> (append to args).
+            </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            </if>
 

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

@@ -0,0 +1,66 @@
+
+##  NAME
+
+`ase-code-refactor` - Refactor Artifacts
+
+##  SYNOPSIS
+
+`ase-code-refactor`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    [`--next`|`-n` *option*]
+    [*task-id*:] *request*
+
+##  DESCRIPTION
+
+The `ase-code-refactor` skill refactors existing artifacts by
+investigating the related code, internalizing refactoring tenets
+(Behavior Preservation, Boy Scout Rule, DRY, SRP, loose coupling,
+clear interfaces, ...), proposing one or more *refactoring approaches*
+with pros and cons, letting the user pick the preferred approach,
+and composing a corresponding *task plan*.
+
+The skill does *not* directly modify source files. It persists the
+plan via `ase_task_save` and then hands off to `ase-task-edit`,
+`ase-task-preflight`, or `ase-task-implement`, as selected by
+`--next`.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically pick the recommended refactoring approach without
+    asking the user via the interactive dialog.
+
+`--next`|`-n` *option*:
+    Automatically choose the next step after composing the plan,
+    where *option* is either `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`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+[*task-id*:] *request*:
+    Description of the refactoring *request*. Optionally prefixed
+    with a *task-id* followed by a colon to bind the resulting plan
+    to a specific task id.
+
+##  EXAMPLES
+
+Refactor a module into smaller files:
+
+```text
+❯ /ase-code-refactor split src/handlers.ts into per-route modules
+```
+
+Refactor under a named task and directly hand off to implementation:
+
+```text
+❯ /ase-code-refactor --next IMPLEMENT cleanup: extract HTTP client into its own class
+```
+
+##  SEE ALSO
+
+`ase-code-craft`, `ase-code-resolve`, `ase-task-edit`,
+`ase-task-preflight`, `ase-task-implement`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-resolve
-argument-hint: "[<task-id>:] <problem>"
+argument-hint: "[--help|-h] [--auto|-a] [--next|-n <option>] [<task-id>:] <problem>"
 description: >
     Resolve Problem:
     Use when user wants a bug fixed or problem resolved.
@@ -17,9 +17,6 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Resolve Problem
-===============
-
 <skill name="ase-code-resolve">
 Resolve Problem
 </skill>
@@ -30,10 +27,6 @@ Resolve Problem
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level software developer*.
-</role>
-
 <objective>
 *Resolve* the following problem:
 <problem><getopt-arguments/></problem>
@@ -60,7 +53,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         identifier like `P1`, `P2`, `T1`, `T2`, ...),
         set <problem-id><problem/></problem-id> and
         <ase-task-id><problem/></ase-task-id>, call the `ase_task_id(id:
-        <ase-task-id/>, session: <ase-session-id/>)` tool from the
+        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
         `ase` MCP server to implicitly switch the task, and then
         call the `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
         the `ase` MCP server to retrieve the previously persisted
@@ -73,7 +66,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ">
         Set <ase-task-id><problem/></ase-task-id> (set task id to problem)
         and <problem></problem> (set problem empty), call the
-        `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
+        `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool
         from the `ase` MCP server to switch the task, and then only
         output the following <template/>:
 
@@ -85,8 +78,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     3.  If <problem/> has the format `<id/>: <text/>` where <id/> matches
         the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
         <problem><text/></problem> and <ase-task-id><id/></ase-task-id>
-        and call the `ase_task_id(id: <ase-task-id/>, session:
-        <ase-session-id/>)` tool from the `ase` MCP server to
+        and call the `ase_task_id(id: "<ase-task-id/>", session:
+        "<ase-session-id/>")` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
 
     4.  If <problem/> is empty,
@@ -103,8 +96,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ">
         Set <ase-task-id/> to a unique task id, derived from <problem/>,
         which consists of two lower-case words concatenated with a
-        `-` character. Then call the `ase_task_id(id: <ase-task-id/>,
-        session: <ase-session-id/>)` tool from the `ase` MCP server to
+        `-` character. Then call the `ase_task_id(id: "<ase-task-id/>",
+        session: "<ase-session-id/>")` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
         </if>
 
@@ -318,7 +311,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         words <words/> of <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: "<content/>")`.
 
     4.  If <problem-id/> is set (i.e. the <problem/> was retrieved from
         `ase_kv_get` in STEP 1.3 via key `ase-issue-<problem-id/>`),
@@ -333,9 +326,26 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    6.  Directly pass-through control to the `ase:ase-task-edit` skill.
-        Set <args></args> (set args to empty). If <getopt-option-next/>
-        is not equal `none`, set <args><args/> --next
-        <getopt-option-next/></args> (append to args). Then call the
-        tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+    6.  Directly pass-through control to the next skill:
+
+        1.  <if condition="<getopt-option-next/> is equal `IMPLEMENT`">
+            Call the tool `Skill(skill: "ase:ase-task-implement")` to
+            *implement* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        2.  <if condition="<getopt-option-next/> is equal `PREFLIGHT`">
+            Call the tool `Skill(skill: "ase:ase-task-preflight")` to
+            *preflight* the freshly composed plan, bypassing `ase-task-edit`.
+            </if>
+
+        3.  <if condition="
+                <getopt-option-next/> is not equal `IMPLEMENT` AND
+                <getopt-option-next/> is not equal `PREFLIGHT`
+            ">
+            Set <args></args> (set args to empty).
+            <if condition="<getopt-option-next/> is not equal `none`">
+            Set <args><args/> --next <getopt-option-next/></args> (append to args).
+            </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            </if>
 

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

@@ -0,0 +1,73 @@
+
+##  NAME
+
+`ase-code-resolve` - Resolve Problem
+
+##  SYNOPSIS
+
+`ase-code-resolve`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    [`--next`|`-n` *option*]
+    [*task-id*:] *problem*
+
+##  DESCRIPTION
+
+The `ase-code-resolve` skill resolves a *bug* or *problem* by
+investigating the related code, internalizing resolution tenets
+(Surgical Changes, No Cleanups, Minimum Flags, Code Adequacy, Origin
+Proximity, ...), proposing one or more *resolution approaches* with
+pros and cons, letting the user pick the preferred approach, and
+composing a corresponding *task plan*.
+
+The *problem* may also be given as a bare issue identifier (e.g. `P1`
+or `T1`) previously produced by `ase-code-analyze` or
+`ase-arch-analyze` and persisted in the `ase` MCP key/value store
+under `ase-issue-<id>`.
+
+The skill does *not* directly modify source files. It persists the
+plan via `ase_task_save` and then hands off to `ase-task-edit`,
+`ase-task-preflight`, or `ase-task-implement`, as selected by
+`--next`.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically pick the recommended resolution approach without
+    asking the user via the interactive dialog.
+
+`--next`|`-n` *option*:
+    Automatically choose the next step after composing the plan,
+    where *option* is either `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`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+[*task-id*:] *problem*:
+    Description of the *problem* to resolve, or a bare issue
+    identifier like `P1` or `T1` previously produced by an analyzer
+    skill. Optionally prefixed with a *task-id* followed by a colon
+    to bind the resulting plan to a specific task id.
+
+##  EXAMPLES
+
+Resolve a free-text problem:
+
+```text
+❯ /ase-code-resolve fix race condition in cache invalidation
+```
+
+Resolve a previously analyzed issue and hand off to implementation:
+
+```text
+❯ /ase-code-resolve --next IMPLEMENT P1
+```
+
+##  SEE ALSO
+
+`ase-code-craft`, `ase-code-refactor`, `ase-code-analyze`,
+`ase-arch-analyze`, `ase-task-edit`, `ase-task-preflight`,
+`ase-task-implement`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-docs-proofread
-argument-hint: "<docs-reference>"
+argument-hint: "[--help|-h] [--auto|-a] <docs-reference>"
 description: >
     Analyze the documents for spelling, punctuation, or grammar errors.
     Use when the user wants to "proofread" or "spellcheck" a document.
@@ -14,11 +14,8 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Proofread Documentation
-=======================
-
 <skill name="ase-docs-proofread">
-Analyze the documents for spelling, punctuation, or grammar errors.
+Analyze documents for spelling, punctuation, or grammar errors
 </skill>
 
 <expand name="getopt"
@@ -27,14 +24,8 @@ Analyze the documents for spelling, punctuation, or grammar errors.
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level proofreader*, specialized in
-checking and correcting the *spelling*, *punctuation* and *grammar* of
-documents.
-</role>
-
 <objective>
-*Analyze* the documents of `<getopt-arguments/>` for problems in their
+*Proofread* the documents of `<getopt-arguments/>` for problems in their
 *spelling*, *punctuation*, or *grammar* and propose corrections.
 </objective>
 

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

@@ -0,0 +1,54 @@
+
+##  NAME
+
+`ase-docs-proofread` - Proofread Documents
+
+##  SYNOPSIS
+
+`ase-docs-proofread`
+    [`--help`|`-h`]
+    [`--auto`|`-a`]
+    *docs-reference*
+
+##  DESCRIPTION
+
+The `ase-docs-proofread` skill analyzes the referenced documents for
+*spelling*, *punctuation*, and *grammar* errors and proposes
+corrections. The investigation is dispatched to a sub-agent
+(`ase:ase-docs-proofread`) so that scanning details do not leak into
+the user-visible transcript.
+
+For each detected problem, the skill renders a unified-diff
+*CORRECTION* preview and either asks the user to `ACCEPT` or `REJECT`
+the proposed correction interactively or — with `--auto` — applies
+all corrections automatically.
+
+##  OPTIONS
+
+`--auto`|`-a`:
+    Automatically apply every proposed correction without asking the
+    user via the interactive dialog.
+
+##  ARGUMENTS
+
+*docs-reference*:
+    A file, directory, or other reference to the documents to
+    proofread.
+
+##  EXAMPLES
+
+Proofread a single document interactively:
+
+```text
+❯ /ase-docs-proofread README.md
+```
+
+Proofread an entire documentation directory automatically:
+
+```text
+❯ /ase-docs-proofread --auto docs/
+```
+
+##  SEE ALSO
+
+`ase-code-lint`, `ase-meta-changes`.