@rse/ase 0.9.10 → 0.9.12

package/dst/ase-statusline.js

@@ -184,8 +184,8 @@ export default class StatuslineCommand {
     }
     /*  parse and validate the --tool option  */
     parseTool(value) {
-        if (value !== "claude" && value !== "copilot")
-            throw new InvalidArgumentError(`invalid --tool value: "${value}" (expected "claude" or "copilot")`);
+        if (value !== "claude" && value !== "copilot" && value !== "codex")
+            throw new InvalidArgumentError(`invalid --tool value: "${value}" (expected "claude", "copilot", or "codex")`);
         return value;
     }
     /*  register commands  */
@@ -196,7 +196,7 @@ export default class StatuslineCommand {
         program
             .command("statusline")
             .description("Render Claude Code or GitHub Copilot CLI statusline from stdin JSON")
-            .option("-t, --tool <tool>", "target tool (\"claude\" or \"copilot\")", toolDflt)
+            .option("-t, --tool <tool>", "target tool (\"claude\" or \"copilot\"; \"codex\" is unsupported)", toolDflt)
             .option("-w, --width <n>", "force terminal width to <n> characters (0 = auto-detect via /dev/tty)", parseInteger("--width"), 0)
             .option("-m, --margin <n>", "reduce maximum used terminal width by <n> characters on each side", parseInteger("--margin"), 2)
             .option("--no-icons", "disable icons in placeholder rendering")
@@ -208,6 +208,10 @@ export default class StatuslineCommand {
             .action(async (lines, opts) => {
             /*  validate target tool  */
             const tool = this.parseTool(opts.tool);
+            /*  OpenAI Codex CLI has no scriptable custom statusline
+                mechanism, so reject the request explicitly  */
+            if (tool === "codex")
+                throw new Error("OpenAI Codex CLI does not support a custom statusline");
             /*  read all of stdin  */
             const input = await readStdin();
             /*  parse JSON data  */

package/dst/ase.js

@@ -15,6 +15,7 @@ import SetupCommand from "./ase-setup.js";
 import StatuslineCommand from "./ase-statusline.js";
 import TaskCommand from "./ase-task.js";
 import ArtifactCommand from "./ase-artifact.js";
+import CompatCommand from "./ase-compat.js";
 import pkg from "../package.json" with { type: "json" };
 /*  globally initialize logger  */
 const log = new Log("ase", "warning", "-");
@@ -51,6 +52,7 @@ const main = async () => {
     new StatuslineCommand(log).register(program);
     new TaskCommand(log).register(program);
     new ArtifactCommand(log).register(program);
+    new CompatCommand().register(program);
     new DiagramCommand(log).register(program);
     /*  parse program arguments  */
     await program.parseAsync(process.argv);

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.10",
+    "version":                              "0.9.12",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -58,6 +58,7 @@
         "which":                            "7.0.0",
         "update-notifier":                  "7.3.1",
         "shell-quote":                      "1.8.4",
+        "get-stdin":                        "10.0.0",
         "proper-lockfile":                  "4.1.2",
         "write-file-atomic":                "8.0.0",
         "pacote":                           "21.5.1",

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

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

package/plugin/.codex-plugin/mcp.json

@@ -0,0 +1,8 @@
+{
+    "mcpServers": {
+        "ase": {
+            "command": "ase",
+            "args":    [ "mcp" ]
+        }
+    }
+}

package/plugin/.codex-plugin/plugin.json

@@ -0,0 +1,17 @@
+{
+    "name":        "ase",
+    "version":     "0.9.12",
+    "description": "Agentic Software Engineering (ASE)",
+    "keywords":    [ "agentic", "software", "engineering" ],
+    "homepage":    "https://ase.tools",
+    "repository":  "https://github.com/rse/ase",
+    "license":     "GPL-3.0",
+    "author": {
+        "name":    "Dr. Ralf S. Engelschall",
+        "email":   "rse@engelschall.com",
+        "url":     "https://engelschall.com"
+    },
+    "skills":      "./skills/",
+    "hooks":       "./hooks/hooks-codex.json",
+    "mcpServers":  "./.codex-plugin/mcp.json"
+}

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

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

package/plugin/hooks/hooks-codex.json

@@ -0,0 +1,67 @@
+{
+    "hooks": {
+        "SessionStart": [
+            {
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "ase hook session-start --tool codex",
+                        "statusMessage": "Loading ASE..."
+                    }
+                ]
+            }
+        ],
+        "SessionEnd": [
+            {
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "ase hook session-end --tool codex",
+                        "statusMessage": "Cleaning up ASE..."
+                    }
+                ]
+            }
+        ],
+        "PreToolUse": [
+            {
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "ase hook pre-tool-use --tool codex"
+                    }
+                ]
+            }
+        ],
+        "PermissionRequest": [
+            {
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "ase hook permission-request --tool codex",
+                        "statusMessage": "Approve ASE..."
+                    }
+                ]
+            }
+        ],
+        "UserPromptSubmit": [
+            {
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "ase hook user-prompt-submit --tool codex"
+                    }
+                ]
+            }
+        ],
+        "Stop": [
+            {
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "ase hook stop --tool codex"
+                    }
+                ]
+            }
+        ]
+    }
+}

package/plugin/meta/ase-dialog.md

@@ -9,6 +9,9 @@ User Dialog
 <if condition="<ase-agent-tool/> is 'copilot'">
     <user-dialog-tool>ask_user</user-dialog-tool>
 </if>
+<if condition="<ase-agent-tool/> is 'codex'">
+    <user-dialog-tool>none</user-dialog-tool>
+</if>
 
 <define name="user-dialog">
 
@@ -138,6 +141,23 @@ Let the *user interactively choose* an answer.
 
         </if>
 
+    -   <if condition="<ase-agent-tool/> is 'codex'">
+
+        OpenAI Codex CLI has *no* interactive user-dialog tool, so you
+        *MUST* *NOT* call any tool here. Instead, render the question and
+        answers as a custom Markdown dialog and let the user reply with a
+        free-text choice -- exactly as defined by the following expansion,
+        passing <spec/> as its question specification, and set <result/> to
+        the result of that custom dialog:
+
+        <expand name="custom-dialog" arg1="--other">
+            <spec/>
+        </expand>
+
+        Do not output anything in this step!
+
+        </if>
+
 </define>
 
 <define name="custom-dialog">

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.10",
+    "version":                              "0.9.12",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

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

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

@@ -52,8 +52,8 @@ for the technology stack to *provide* the *needed functionality*
             Functionality: Which functionality should the components provide?
             <answer-1/>: (grounded candidate functionality 1)
             <answer-2/>: (grounded candidate functionality 2)
-            <answer-3/>: (grounded candidate functionality 2)
-            <answer-4/>: (grounded candidate functionality 3)
+            <answer-3/>: (grounded candidate functionality 3)
+            <answer-4/>: (grounded candidate functionality 4)
         </expand>
 
         Then use the <result/> and its corresponding grounded candidate

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

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

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

@@ -249,7 +249,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         a question with the following custom dialog, where per
         approach A<n/>, you determine an ultra brief summary
         <short-summary/> and then use the answer option `A<n/>:
-        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        ⚝ **RECOMMENDATION** ⚝ - <short-summary/>` for your
         recommended approach plus zero or more answer options `A<n/>:
         <short-summary/>` for all other approaches:
 
@@ -343,11 +343,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining
-                tokens (joined back with `,`, or `none` if empty).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>

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

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

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

@@ -18,13 +18,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-insight">
 Project Insight
 </skill>
 
+<expand name="getopt" arg1="ase-code-insight">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Give *insights* into the project through the source code of $ARGUMENTS.
+Give *insights* into the project through the source code of <getopt-arguments/>.
 </objective>
 
 <flow>

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

@@ -248,9 +248,15 @@ related to a set of code quality aspects.
             -   <if condition="<result/> starts with 'OTHER'">
                 Generate a *new* proposal for the *same* <item/>
                 (incorporating the user's free-text hint from <result/> if
-                provided via the "OTHER" prefix) and loop back to substep 2
-                of this iteration. There is *no* cap on refinement rounds -
-                keep refining until the user picks `ACCEPT` or `REJECT`.
+                provided via the "OTHER" prefix). *Reassign* <description/>
+                and <change-set/> to reflect this refined proposal (each
+                change-hunk's `old_text` stays anchored to the existing
+                text at its `file`:`line`; `new_text` carries the
+                refinement) so that the substep 2/3 rebuild renders the new
+                <diff/> and any `Edit` applies the new proposal rather than
+                the original. Then loop back to substep 2 of this iteration.
+                There is *no* cap on refinement rounds - keep refining until
+                the user picks `ACCEPT` or `REJECT`.
                 </if>
 
             -   <if condition="

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

@@ -238,7 +238,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         a question with the following custom dialog, where per
         approach A<n/>, you determine an ultra brief summary
         <short-summary/> and then use the answer option `A<n/>:
-        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        ⚝ **RECOMMENDATION** ⚝ - <short-summary/>` for your
         recommended approach plus zero or more answer options `A<n/>:
         <short-summary/>` for all other approaches:
 
@@ -332,11 +332,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining
-                tokens (joined back with `,`, or `none` if empty).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>

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

@@ -60,14 +60,15 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     1.  If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue
         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` MCP server to implicitly switch the task, and then
-        call the `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
+        <ase-task-id><problem/></ase-task-id>, then call the
+        `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
         the `ase` MCP server to retrieve the previously persisted
         problem description. If the returned `text` is non-empty, set
-        <problem><text/></problem>, otherwise complain to the user that
-        no analyzer result exists for <problem-id/> and stop processing.
+        <problem><text/></problem> 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, otherwise
+        complain to the user that no analyzer result exists for
+        <problem-id/> and stop processing.
 
     2.  <if condition="
             <problem/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
@@ -288,7 +289,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         a question with the following custom dialog, where per
         approach A<n/>, you determine an ultra brief summary
         <short-summary/> and then use the answer option `A<n/>:
-        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        ⚝ **RECOMMENDATION** ⚝ - <short-summary/>` for your
         recommended approach plus zero or more answer options `A<n/>:
         <short-summary/>` for all other approaches:
 
@@ -389,11 +390,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining
-                tokens (joined back with `,`, or `none` if empty).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>

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

@@ -188,9 +188,15 @@ Analyze documents for spelling, punctuation, or grammar errors
 
                 Generate a *new* proposal for the *same* <item/>,
                 incorporating the user's free-text hint from <result/>
-                after the "OTHER:" prefix, and *go back* to substep 2 of
-                this `for`-iteration. There is *no* cap on refinement rounds -
-                keep refining until the user picks `ACCEPT` or `REJECT`.
+                after the "OTHER:" prefix. *Reassign* <description/>,
+                <old-text/>, and <new-text/> to reflect this refined
+                proposal (<old-text/> stays anchored to the existing text
+                at <file/>:<line/>; <new-text/> and <description/> carry the
+                refinement) so the subsequent rendering and any `Edit` use
+                the new proposal rather than the original. Then *go back* to
+                substep 2 of this `for`-iteration. There is *no* cap on
+                refinement rounds - keep refining until the user picks
+                `ACCEPT` or `REJECT`.
 
                 </if>
 

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

@@ -129,10 +129,9 @@ Honor the following tenets throughout the brainstorming:
 
             <expand name="custom-dialog" arg1="--other">
                 <facet-M/>: <question-M/>
-                <answer-M-1/>: (first grounded candidate answer)
-                <answer-M-2/>: (second grounded candidate answer)
-                <answer-M-3/>: (third grounded candidate answer)
-                <answer-M-4/>: (fourth grounded candidate answer)
+                <answer-M-1/>: (grounded candidate answer 1)
+                <answer-M-2/>: (grounded candidate answer 2)
+                [...]
             </expand>
 
         4.  Dispatch on the dialog <result/>:

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

@@ -16,11 +16,16 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-changelog">
 Update ChangeLog Entries
 </skill>
 
+<expand name="getopt" arg1="ase-meta-changelog">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Help to complete, consolidate and sort *ChangeLog* entries of the most
 recent *ChangeLog* section, based on underlying *Git* commits and staged
@@ -81,11 +86,17 @@ Processing
     the Git *commits* plus the currently already staged changes in the Git
     *index*, but *ignore* the Git *stash* and still unstaged changes.
 
-    For finding the corresponding Git *commits*, use the `N.M.K` from the
-    *second* level-2 header in the *ChangeLog* file as the corresponding
-    Git tag and then check all Git commits between `HEAD` and this tag
-    with the command `git log N.M.K..HEAD --numstat --pretty=format:'%h:
-    %s'`.
+    For finding the corresponding Git *commits*, first determine the
+    correct baseline Git tag. Take the `N.M.K` from the *first* (most
+    recent) level-2 header in the *ChangeLog* file and check whether a
+    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*
+    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
+    command `git log N.M.K..HEAD --numstat --pretty=format:'%h: %s'`.
 
     For finding the corresponding staged Git *changes* in the Git
     *index*, use the command `git diff --cached --numstat`, but silently

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

@@ -14,13 +14,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-chat">
 Query Foreign LLM for Chat
 </skill>
 
+<expand name="getopt" arg1="ase-meta-chat">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Query foreign LLM for: <query>$ARGUMENTS</query>
+Query foreign LLM for: <query><getopt-arguments/></query>
 </objective>
 
 1.  You *MUST* *NOT* output anything in this step.

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

@@ -12,11 +12,16 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-commit">
 Git Commit
 </skill>
 
+<expand name="getopt" arg1="ase-meta-commit">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Help to *craft* a *concise commit message* for the
 currently staged Git changes.