@rse/ase 1.0.7 → 2.0.0

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

@@ -65,4 +65,4 @@ Route a planning intent to the matching commands:
 ##  SEE ALSO
 
 [`ase-help-skill`](../ase-help-skill/help.md), [`ase-meta-proximity`](../ase-meta-proximity/help.md), [`ase-meta-search`](../ase-meta-search/help.md),
-[`ase-code-craft`](../ase-code-craft/help.md).
+[`ase-task-edit`](../ase-task-edit/help.md).

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

@@ -29,9 +29,6 @@
 ○   `ase-code-lint`:       Lint Source Code
 ○   `ase-code-explain`:    Explain Source Code
 ○   `ase-code-insight`:    Project Insight
-○   `ase-code-craft`:      Craft Source Code
-○   `ase-code-refactor`:   Refactor Artifacts
-○   `ase-code-resolve`:    Resolve Problem
 ○   `ase-code-edit`:       Edit Source Code
 ○   `ase-sync-import`:     Import Foreign Sources into Artifact Set
 ○   `ase-sync-reconcile`:  Reconcile Artifact Set to Artifact Set
@@ -44,11 +41,13 @@
 ○   `ase-docs-distill`:    Distill Document Key Points
 
 ⎈   **VERSION CONTROL**
-○   `ase-meta-changelog`:  Update ChangeLog Entries
-○   `ase-meta-commit`:     Git Commit Message
-○   `ase-meta-diff`:       Summarize Diff
-○   `ase-meta-review`:     Review Staged Changes
-○   `ase-code-dissect`:    Dissect a Change Set
+○   `ase-repo-changelog`:  Update ChangeLog Entries
+○   `ase-repo-commit`:     Git Commit Message
+○   `ase-repo-diff`:       Summarize Diff
+○   `ase-repo-review`:     Review Changes
+○   `ase-repo-dissect`:    Dissect a Change Set
+○   `ase-repo-merge`:      Merge a Branch
+○   `ase-repo-resolve`:    Resolve Merge Conflicts
 
 ⎈   **TASK MANAGEMENT**
 ○   `ase-task-id`:         Configure Task Id
@@ -56,11 +55,15 @@
 ○   `ase-task-view`:       View a Task Plan
 ○   `ase-task-edit`:       Iteratively Edit a Task Plan
 ○   `ase-task-grill`:      Iteratively Grill a Task Plan
+○   `ase-task-research`:   Research a Topic for a Task Plan
 ○   `ase-task-condense`:   Condense a Task Plan
 ○   `ase-task-dissect`:    Dissect a Task Plan
+○   `ase-task-estimate`:   Estimate the Effort of a Task Plan
 ○   `ase-task-reboot`:     Reboot a Task Plan
-○   `ase-task-preflight`:  Preflight a Task Plan
 ○   `ase-task-implement`:  Implement a Task Plan
+○   `ase-task-integrate`:  Integrate a Task Change Set
+○   `ase-task-status`:     Configure Task Status
+○   `ase-task-assign`:     Assign a Task Plan
 ○   `ase-task-rename`:     Rename a Task Plan
 ○   `ase-task-delete`:     Delete a Task Plan
 

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

@@ -285,7 +285,7 @@ Honor the following tenets throughout the brainstorming:
         into nothing and hence emit no output at all):
 
         <ase-tpl-hint level="normal">
-        To turn the recommended idea into a plan, use `/ase-task-edit`; to turn it directly into code, use `/ase-code-craft`.
+        To turn the recommended idea into a plan, use `/ase-task-edit`; to turn it directly into code, use `/ase-code-edit`.
         </ase-tpl-hint>
 
     </step>

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

@@ -5,8 +5,8 @@ description: >
     List, get, set, or delete the layered ASE configuration values across
     the user/project/task/session scope chain.
     Use when the user wants to "configure" ASE, or to inspect or change a
-    configuration key like `agent.persona`, `agent.guidance`, `agent.task`,
-    or `project.boxing`.
+    configuration key like `agent.persona`, `agent.guidance`,
+    `project.boxing`, or `project.task.lifecycle`.
 user-invocable: true
 disable-model-invocation: false
 effort: high
@@ -53,8 +53,7 @@ Procedure
         <if condition="<getopt-option-scope/> is empty">
         Set <scope>session:<ase-session-id/></scope>. Reads then cascade
         `user` -> `project` -> `session`, and writes land on the *session*
-        layer -- the only layer on which the `agent.task` and `agent.skill`
-        keys are writable at all.
+        layer.
         </if>
         <else>
         Set <scope><getopt-option-scope/></scope>, forwarding the given

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

@@ -27,13 +27,14 @@ return the first value that is defined; writes are always confined to
 the strongest (target) scope of the chain.
 
 The recognized keys are grouped under `project.*` (`project.id`,
-`project.name`, `project.boxing`, and the
-`project.artifact.`*kind*`.{basedir,files}` globs) and `agent.*`
-(`agent.persona`, `agent.guidance`, `agent.task`, and `agent.skill`).
+`project.name`, `project.boxing`, `project.task.lifecycle`,
+`project.task.idscheme`, `project.task.default.{source,changeset,target}`,
+and the `project.artifact.`*kind*`.{basedir,files}`
+globs) and `agent.*` (`agent.persona` and `agent.guidance`).
 Some keys are writable on selected scopes only; in particular
-`agent.task` and `agent.skill` are writable on a `session` scope only,
-and the `project.artifact.*` globs are writable on the `user` and
-`project` scopes only.
+the `project.artifact.*` globs are writable on the `user` and
+`project` scopes only. The internal session state, like the active
+task id (see `ase-task-id`), is not part of the configuration.
 
 The three keys steering the behaviour of the agent itself accept fixed
 value sets: `agent.persona` selects the *communication style* and is one
@@ -46,7 +47,22 @@ pyramid-structured `journalist`, the brief, factual, and abbreviating
 `project.boxing` selects the artifact transparency and is one of `white`,
 `grey`, or `black`. Setting `agent.persona`, `agent.guidance`, or
 `project.boxing` takes effect immediately, i.e. still within the running
-session.
+session. Additionally, `project.task.lifecycle` selects the task plan
+lifecycle and is one of `solo` (the default), `team`, or `enterprise`; it is
+exported at session start as `<ase-project-task-lifecycle/>`. Finally,
+`project.task.idscheme` selects the scheme of newly generated task ids and is one
+of `slug[:<words>]` (the default, the first *words* (default: 2) words of
+the task title, lower-cased and joined with `-`), `seq[:<template>]` (a
+continuously increasing sequence number, rendered through a sprintf-style
+*template* like `FOO-%03d`, `#%d`, or `%d` (the default)), or `any` (an
+arbitrary unique id chosen by the agent). Additionally,
+`project.task.default.{source,changeset,target}` select the defaults of
+the `Source:`, `Changeset:`, and `Target:` task plan keys (`worktree`,
+`worktree`, and `source` by default), which an absent key reads as, where
+a `branch:<name>` or `attachment:<name>` value can carry the placeholder
+`{id}` of the task id (e.g., `branch:cs-{id}` for a branch per task); they
+are exported at session start as
+`<ase-project-task-default-{source,changeset,target}/>`.
 
 The following *operations* exist:
 
@@ -82,8 +98,7 @@ preset-bootstrapping operation that stays a shell concern next to
     the strongest explicitly requested term. If the option is
     omitted, the chain of the *current session* (`session:`*id*) is used,
     so that reads see the full `user` -> `project` -> `session` cascade
-    and writes -- including those to the session-only keys `agent.task`
-    and `agent.skill` -- land on the session layer.
+    and writes land on the session layer.
 
 ##  ARGUMENTS
 
@@ -97,7 +112,7 @@ preset-bootstrapping operation that stays a shell concern next to
 ##  SCENARIOS
 
 -   You want the ASE configuration inspected or changed
--   You want the persona, guidance, or boxing switched for a session
+-   You want the persona, guidance, boxing, or task lifecycle switched for a session
 -   You want a configuration value persisted at user or project scope
 -   You want to see which scope supplies each effective value
 
@@ -133,6 +148,12 @@ Persist the guidance level for the whole project instead:
 ❯ /ase-meta-config --scope project set agent.guidance minimal
 ```
 
+Persist the task lifecycle for the whole project:
+
+```text
+❯ /ase-meta-config --scope project set project.task.lifecycle team
+```
+
 Remove a value from the user-level configuration:
 
 ```text

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

@@ -1,9 +1,9 @@
 ---
 name: ase-meta-mint
-argument-hint: "[--help|-h] [--type|-t uuid|sha1|const|var|class|func|path|name] [--count|-c <count>] [<hint>]"
+argument-hint: "[--help|-h] [--type|-t uuid|sha1|nanoid|const|var|class|func|path|name] [--count|-c <count>] [<hint>]"
 description: >
     Mint an identifier or a name of a requested type out of a free-text
-    hint: a UUID, a SHA-1 digest, a constant, variable, function, or
+    hint: a UUID, a SHA-1 digest, a NanoId-style hash, a constant, variable, function, or
     class identifier, a path component, or a product-like name. Use when
     the user wants an identifier, id, symbol, slug, or name "minted",
     "coined", "derived", or "generated" from a description.
@@ -22,7 +22,7 @@ Mint an Identifier or Name
 
 <expand name="getopt"
     arg1="ase-meta-mint"
-    arg2="--type|-t=(uuid|sha1|const|var|class|func|path|name) --count|-c=1">
+    arg2="--type|-t=(uuid|sha1|nanoid|const|var|class|func|path|name) --count|-c=1">
     $ARGUMENTS
 </expand>
 
@@ -59,12 +59,12 @@ following hint:
 
     </step>
 
-2.  <step id="STEP 2: Mint Hash-Derived Identifiers" condition="<type/> is `uuid` or `sha1`">
+2.  <step id="STEP 2: Mint Hash-Derived Identifiers" condition="<type/> is `uuid`, `sha1`, or `nanoid`">
 
     1.  Call the `ase_mint(type: "<type/>", hint: "<hint/>", count:
         <count/>)` tool of the `ase` MCP server and set <results/> to
         the returned lines of its `text` output, one identifier per
-        line. You *MUST* *NOT* derive a UUID or a SHA-1 digest yourself
+        line. You *MUST* *NOT* derive a UUID, a SHA-1 digest, or a NanoId-style hash yourself
         -- only the tool hashes correctly and reproducibly.
 
     2.  <if condition="a line of the `text` output starts with `WARNING:`">

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

@@ -7,7 +7,7 @@
 
 `ase-meta-mint`
     [`--help`|`-h`]
-    [`--type`|`-t` `uuid`|`sha1`|`const`|`var`|`class`|`func`|`path`|`name`]
+    [`--type`|`-t` `uuid`|`sha1`|`nanoid`|`const`|`var`|`class`|`func`|`path`|`name`]
     [`--count`|`-c` *count*]
     [*hint*]
 
@@ -17,7 +17,7 @@ The `ase-meta-mint` skill *mints* an identifier or a name of a requested
 type out of the free-text *hint* formed by the positional arguments. It
 dispatches on `--type` and emits the generated strings as its result.
 
-The two *hash-derived* types are delegated to the `ase_mint` tool of the
+The three *hash-derived* types are delegated to the `ase_mint` tool of the
 `ase` MCP server, which derives them reproducibly instead of guessing
 them:
 
@@ -30,6 +30,11 @@ them:
 -   `sha1`:
     the 40-character hexadecimal *SHA-1* digest of the *hint*.
 
+-   `nanoid`:
+    the 10-character, *NanoId*-style *base62* hash of the *hint* (its
+    *SHA-1* digest, *base62*-encoded and truncated), a short but still
+    reproducible identifier.
+
 The six *linguistic* types are derived by the skill itself: the *hint*
 is distilled into its essential words, which are then assembled
 according to the conventions of the type:
@@ -63,7 +68,7 @@ a random *UUID V4* without one.
 
 ##  OPTIONS
 
-`--type`|`-t` `uuid`|`sha1`|`const`|`var`|`class`|`func`|`path`|`name`:
+`--type`|`-t` `uuid`|`sha1`|`nanoid`|`const`|`var`|`class`|`func`|`path`|`name`:
     Select the type of the minted identifier or name (default: `uuid`).
 
 `--count`|`-c` *count*:
@@ -84,7 +89,7 @@ a random *UUID V4* without one.
 
 ##  SCENARIOS
 
--   You need a stable, reproducible UUID or SHA-1 digest for a concept
+-   You need a stable, reproducible UUID, SHA-1 digest, or short hash for a concept
 -   You need a well-formed constant, variable, function, or class identifier
 -   You need a path component or slug derived from a description
 -   You need a catchy product name for a new component or tool
@@ -111,4 +116,4 @@ Mint three product name candidates:
 
 ##  SEE ALSO
 
-[`ase-task-id`](../ase-task-id/help.md), [`ase-meta-brainstorm`](../ase-meta-brainstorm/help.md), [`ase-code-craft`](../ase-code-craft/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md).
+[`ase-task-id`](../ase-task-id/help.md), [`ase-meta-brainstorm`](../ase-meta-brainstorm/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md).

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

@@ -86,4 +86,4 @@ committing early to the wrong root cause:
 
 ##  SEE ALSO
 
-[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).
+[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

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

@@ -42,7 +42,7 @@ References
 
 -   The following <sample/> is a *reference skill* demonstrating the
     usual *layout* of a generated workflow skill -- its frontmatter, its
-    `ase meta` preamble, and the indentation of its `<flow>`:
+    `ase util meta` preamble, and the indentation of its `<flow>`:
 
     <sample>
     @${CLAUDE_SKILL_DIR}/sample.md
@@ -94,7 +94,7 @@ installation path. It therefore *MUST* strictly follow this contract:
 
     <if condition="<ase-agent-tool/> is `codex`">
     Emit *only* an `allowed-tools` field, carrying the space-separated
-    string `Bash(ase meta *)`, because *OpenAI Codex* accepts *no*
+    string `Bash(ase util meta *)`, because *OpenAI Codex* accepts *no*
     frontmatter fields besides `name`, `description`, `license`,
     `allowed-tools`, and `metadata`.
     </if>
@@ -115,14 +115,14 @@ installation path. It therefore *MUST* strictly follow this contract:
     Emit an `argument-hint` derived from the declared options and
     arguments, plus `user-invocable: true`, `disable-model-invocation:
     false`, and an `allowed-tools` list which *always* contains
-    `"Bash(ase meta *)"` plus `"Skill"` and/or `"Agent"` whenever the
+    `"Bash(ase util meta *)"` plus `"Skill"` and/or `"Agent"` whenever the
     workflow emits `<skill/>` and/or `<agent/>` invocations, plus any
     further tool the workflow actually uses.
     </else>
 
 -   **Preamble**: the generated skill has to pull in the ASE meta
-    definitions through the `ase meta` command, because it resolves them
-    from the bundled tool package, whereas the
+    definitions through the `ase util meta` command, because it resolves
+    them from the bundled tool package, whereas the
     `@${CLAUDE_SKILL_DIR}/../../meta/` includes used *inside* the ASE
     plugin have *no* resolvable path from outside of it. Append further
     meta names only when the workflow needs them (`dialog` for a
@@ -141,7 +141,7 @@ installation path. It therefore *MUST* strictly follow this contract:
     <preamble-block>
     *IMPORTANT*: *Before* anything else, run the shell command...
 
-    `ase meta control skill getopt`
+    `ase util meta control skill getopt`
 
     ...and treat its *entire* output as if it were written here. It
     defines the control flow constructs, the skill conventions, and the
@@ -150,7 +150,7 @@ installation path. It therefore *MUST* strictly follow this contract:
     </if>
 
     <else>
-    Emit the *single* line ``!`ase meta control skill getopt` `` as the
+    Emit the *single* line ``!`ase util meta control skill getopt` `` as the
     first body line.
     </else>
 

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

@@ -44,8 +44,8 @@ derivation but never restricts it: arbitrary non-ASE actions and
 unlisted transitions stay allowed.
 
 The generated skill is *independent* of the ASE plugin installation path:
-it loads the ASE meta definitions through the `ase meta` command instead
-of plugin-relative includes.
+it loads the ASE meta definitions through the `ase util meta` command
+instead of plugin-relative includes.
 
 The skill is *portable* across the supported agent tools, because
 *Anthropic Claude Code*, *GitHub Copilot*, and *OpenAI Codex* differ in
@@ -62,7 +62,7 @@ agent tool:
     ``!`...`` construct before the skill content reaches the model. The
     other agent tools receive it verbatim and would silently leave it
     unexpanded, so they instead get an explicit instruction to run
-    `ase meta ...` themselves before anything else.
+    `ase util meta ...` themselves before anything else.
 
 ##  OPTIONS
 
@@ -121,4 +121,4 @@ Generate a user-wide skill and overwrite a previous generation:
 ##  SEE ALSO
 
 [`ase-help-intent`](../ase-help-intent/help.md), [`ase-help-skill`](../ase-help-skill/help.md),
-[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-task-implement`](../ase-task-implement/help.md).
+[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-implement`](../ase-task-implement/help.md).

package/plugin/skills/ase-meta-workflow/sample.md

@@ -6,10 +6,10 @@ description: >
 user-invocable: true
 disable-model-invocation: false
 allowed-tools:
-    - "Bash(ase meta *)"
+    - "Bash(ase util meta *)"
 ---
 
-!`ase meta control skill getopt`
+!`ase util meta control skill getopt`
 
 <purpose name="optimizer">
 Analyze and Resolve Source Code Problems
@@ -48,7 +48,7 @@ Analyze and Resolve Source Code Problems
             isolation="worktree"
             run_in_background=true>
 
-            1.  Run <skill name="ase:ase-code-resolve" args="-a <id/>-P<n/>"/>
+            1.  Run <skill name="ase:ase-task-edit" args="--next DONE <id/>-P<n/>: <id/>-P<n/>"/>
 
             2.  Run <skill name="ase:ase-task-implement" args="<id/>-P<n/>"/>
 

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

@@ -19,14 +19,16 @@ START               -> ase-docs-shorten
 START               -> ase-docs-refine
 START               -> ase-docs-proofread
 START               -> ase-docs-distill
-START               -> ase-meta-review
-START               -> ase-meta-diff
-START               -> ase-meta-changelog
-START               -> ase-meta-commit
+START               -> ase-repo-review
+START               -> ase-repo-diff
+START               -> ase-repo-changelog
+START               -> ase-repo-commit
 START               -> ase-meta-proximity
 START               -> ase-meta-mint
 START               -> ase-meta-workflow
-START               -> ase-code-dissect
+START               -> ase-repo-dissect
+START               -> ase-repo-merge
+START               -> ase-repo-resolve
 ase-help-skill      -> END
 ase-meta-config     -> END
 ase-meta-why        -> END
@@ -48,14 +50,16 @@ ase-docs-shorten    -> END
 ase-docs-refine     -> END
 ase-docs-proofread  -> END
 ase-docs-distill    -> END
-ase-meta-review     -> END
-ase-meta-diff       -> END
-ase-meta-changelog  -> END
-ase-meta-commit     -> END
+ase-repo-review     -> END
+ase-repo-diff       -> END
+ase-repo-changelog  -> END
+ase-repo-commit     -> END
 ase-meta-proximity  -> END
 ase-meta-mint       -> END
 ase-meta-workflow   -> END
-ase-code-dissect    -> END
+ase-repo-dissect    -> END
+ase-repo-merge      -> END
+ase-repo-resolve    -> END
 START               -> SKETCH
 START               -> TASK
 START               -> ase-sync-import
@@ -64,12 +68,12 @@ ARTIFACT            -> ase-arch-analyze
 ARTIFACT            -> ase-code-analyze
 ase-arch-analyze    -> SKETCH
 ase-code-analyze    -> SKETCH
-SKETCH              -> ase-code-craft
-SKETCH              -> ase-code-refactor
-SKETCH              -> ase-code-resolve
-ase-code-craft      -> APPROACHES
-ase-code-refactor   -> APPROACHES
-ase-code-resolve    -> APPROACHES
+SKETCH              -> ase-task-edit
+SKETCH              -> ase-code-edit
+SKETCH              -> ase-spec-edit
+ase-task-edit       -> APPROACHES
+ase-code-edit       -> ARTIFACT
+ase-spec-edit       -> ARTIFACT
 APPROACHES          -> TASK
 TASK                -> ase-task-id
 ase-task-id         -> TASK
@@ -84,13 +88,13 @@ ase-task-dissect    -> TASK
 TASK                -> ase-task-reboot
 ase-task-reboot     -> TASK
 TASK                -> ase-task-implement
-TASK                -> ase-task-preflight
-ase-task-preflight  -> TASK
+TASK                -> ase-task-integrate
 TASK                -> ase-task-view
 TASK                -> ase-task-list
 TASK                -> ase-task-rename
 TASK                -> ase-task-delete
 ase-task-implement  -> ARTIFACT
+ase-task-integrate  -> ARTIFACT
 ase-task-view       -> END
 ase-task-list       -> END
 ase-task-rename     -> END

package/plugin/skills/{ase-meta-changelog → ase-repo-changelog}/SKILL.md

@@ -1,10 +1,11 @@
 ---
-name: ase-meta-changelog
+name: ase-repo-changelog
 argument-hint: "[--help|-h]"
 description: >
     Update ChangeLog entries in CHANGELOG.md files
 user-invocable: true
 disable-model-invocation: false
+model: sonnet
 effort: high
 allowed-tools:
     - "Bash(git log *)"
@@ -20,11 +21,11 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-<purpose name="ase-meta-changelog">
+<purpose name="ase-repo-changelog">
 Update ChangeLog Entries
 </purpose>
 
-<expand name="getopt" arg1="ase-meta-changelog">
+<expand name="getopt" arg1="ase-repo-changelog">
     $ARGUMENTS
 </expand>
 

package/plugin/skills/{ase-meta-changelog → ase-repo-changelog}/help.md

@@ -1,16 +1,16 @@
 
 ##  NAME
 
-`ase-meta-changelog` - Update ChangeLog Entries
+`ase-repo-changelog` - Update ChangeLog Entries
 
 ##  SYNOPSIS
 
-`ase-meta-changelog`
+`ase-repo-changelog`
     [`--help`|`-h`]
 
 ##  DESCRIPTION
 
-The `ase-meta-changelog` skill helps to *complete*, *consolidate*, and
+The `ase-repo-changelog` skill helps to *complete*, *consolidate*, and
 *sort* the entries of the most recent section of a `CHANGELOG.md`
 file, based on the underlying *Git* commits and the currently staged
 changes in the Git *index*.
@@ -34,9 +34,9 @@ date.
 Update the most recent ChangeLog section:
 
 ```text
-❯ /ase-meta-changelog
+❯ /ase-repo-changelog
 ```
 
 ##  SEE ALSO
 
-[`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md).
+[`ase-repo-commit`](../ase-repo-commit/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md).

package/plugin/skills/{ase-meta-commit → ase-repo-commit}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ase-meta-commit
+name: ase-repo-commit
 argument-hint: "[--help|-h]"
 description: >
     Determine commit message for staged Git changes.
@@ -15,11 +15,11 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-<purpose name="ase-meta-commit">
+<purpose name="ase-repo-commit">
 Git Commit
 </purpose>
 
-<expand name="getopt" arg1="ase-meta-commit">
+<expand name="getopt" arg1="ase-repo-commit">
     $ARGUMENTS
 </expand>
 
@@ -42,7 +42,7 @@ currently staged Git changes.
     Only output the following <template/> and then *STOP* immediately:
 
     <template>
-    ⧉ **ASE**: ✪ skill: **ase-meta-commit**, ▶ status: **no changes to commit**
+    ⧉ **ASE**: ✪ skill: **ase-repo-commit**, ▶ status: **no changes to commit**
     </template>
     </if>
 
@@ -55,7 +55,7 @@ currently staged Git changes.
     `<type/>: <summary/>`
 
     The known <type/>s (kept deliberately in sync with the intent groups
-    of the `ase-meta-diff` and `ase-meta-changelog` skills) and their
+    of the `ase-repo-diff` and `ase-repo-changelog` skills) and their
     usual corresponding kind of change are:
 
     -   `FEATURE`:     new        functionality or configuration
@@ -90,7 +90,7 @@ currently staged Git changes.
         sub-package) and is *not* itself part of the staged changes
     ">
     <ase-tpl-hint level="normal">
-    The staged changes do not touch `CHANGELOG.md` -- use `/ase-meta-changelog` to update its entries before committing.
+    The staged changes do not touch `CHANGELOG.md` -- use `/ase-repo-changelog` to update its entries before committing.
     </ase-tpl-hint>
     </if>
 

package/plugin/skills/{ase-meta-commit → ase-repo-commit}/help.md

@@ -1,16 +1,16 @@
 
 ##  NAME
 
-`ase-meta-commit` - Git Commit Message
+`ase-repo-commit` - Git Commit Message
 
 ##  SYNOPSIS
 
-`ase-meta-commit`
+`ase-repo-commit`
     [`--help`|`-h`]
 
 ##  DESCRIPTION
 
-The `ase-meta-commit` skill helps to *craft* a *concise commit
+The `ase-repo-commit` skill helps to *craft* a *concise commit
 message* for the currently staged Git changes. It inspects the
 output of `git diff --cached` and produces a single-line message of
 the form `<type>: <summary>` where *type* is one of `FEATURE`,
@@ -29,9 +29,9 @@ trailing period or Markdown formatting.
 Craft a commit message for the currently staged changes:
 
 ```text
-❯ /ase-meta-commit
+❯ /ase-repo-commit
 ```
 
 ##  SEE ALSO
 
-[`ase-meta-changelog`](../ase-meta-changelog/help.md).
+[`ase-repo-changelog`](../ase-repo-changelog/help.md).

package/plugin/skills/{ase-meta-diff → ase-repo-diff}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ase-meta-diff
+name: ase-repo-diff
 argument-hint: "[--help|-h] [--coherence|-c] [--risk|-r] [--blast|-b]"
 description: >
     Summarize the currently staged Git changes as a human-readable,
@@ -21,12 +21,12 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-<purpose name="ase-meta-diff">
+<purpose name="ase-repo-diff">
 Summarize Diff
 </purpose>
 
 <expand name="getopt"
-    arg1="ase-meta-diff"
+    arg1="ase-repo-diff"
     arg2="--coherence|-c --risk|-r --blast|-b">
     $ARGUMENTS
 </expand>
@@ -68,7 +68,7 @@ Procedure
         Only output the following <template/> and then *STOP* immediately:
 
         <template>
-        ⧉ **ASE**: ✪ skill: **ase-meta-diff**, ▶ status: **no changes to summarize**
+        ⧉ **ASE**: ✪ skill: **ase-repo-diff**, ▶ status: **no changes to summarize**
         </template>
         </if>
 
@@ -361,7 +361,7 @@ Procedure
     into nothing and hence emit no output at all):
 
     <ase-tpl-hint level="normal">
-    For a human-reviewer-style critique of the very same staged changes, with an approve/reject verdict, use `/ase-meta-review`.
+    For a human-reviewer-style critique of the very same staged changes, with an approve/reject verdict, use `/ase-repo-review`.
     </ase-tpl-hint>
 
     <if condition="
@@ -370,7 +370,7 @@ Procedure
         <getopt-option-blast/> is not equal `true`
     ">
     <ase-tpl-hint level="verbose">
-    Use `/ase-meta-diff --coherence --risk --blast` to additionally scrutinize the intent coherence, the risk profile, and the blast radius of the staged changes.
+    Use `/ase-repo-diff --coherence --risk --blast` to additionally scrutinize the intent coherence, the risk profile, and the blast radius of the staged changes.
     </ase-tpl-hint>
     </if>