@rse/ase 0.9.58 → 0.9.60

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-craft
-argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--direct|-D] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--direct|-D] [--interactive|-i] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
 description: >
     Craft Source Code:
     Use when user wants to "create", "add", or "craft" a new feature from scratch.
@@ -24,7 +24,7 @@ Craft Source Code
 
 <expand name="getopt"
     arg1="ase-code-craft"
-    arg2="--auto|-a --dry|-d --direct|-D --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
+    arg2="--auto|-a --dry|-d --direct|-D --interactive|-i --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)...">
     $ARGUMENTS
 </expand>
 
@@ -34,6 +34,11 @@ to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to
 `IMPLEMENT,DELETE`. Do not output anything.
 </if>
 
+<if condition="<getopt-option-interactive/> is equal `true`">
+The `--interactive`/`-i` flag *implies* the `--direct`/`-D` mode: set
+<getopt-option-direct/> to `true`. Do not output anything.
+</if>
+
 <objective>
 From scratch *craft* the following feature:
 <feature><getopt-arguments/></feature>
@@ -48,8 +53,9 @@ Procedure
 
 <if condition="<getopt-option-direct/> is not equal to 'true'">
 You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
-filesystem-modifying tool during this entire skill. The *only*
-permitted way to persist artifacts is via `ase_task_save(...)`.
+filesystem-modifying tool, nor execute any filesystem-modifying
+shell command, during this entire skill. The *only* permitted way
+to persist artifacts is via the `ase_task_save(...)` MCP tool.
 </if>
 <else>
 The `--direct`/`-D` mode applies the crafting *in place*, so STEP 4
@@ -162,7 +168,35 @@ crafting actually demands, and you *MUST* *NOT* call
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **changes directly applied**
         </template>
 
-    3.  Then *IMMEDIATELY* *STOP* all further skill processing. You
+    3.  <if condition="<getopt-option-interactive/> is equal `true`">
+        Enter the *interactive crafting loop*:
+
+        <while condition="`true`">
+
+        1.  In the following, you *MUST* *NOT* use your built-in
+            <user-dialog-tool/> tool! Instead, you *MUST* just show a
+            custom dialog according to the expanded `custom-dialog`
+            definition. You *MUST* closely follow this definition.
+
+            Ask the user for the next change with the following
+            custom dialog:
+
+            <expand name="custom-dialog" arg1="--other">
+                Next Change: What is the next change to craft?
+                DONE: Finish the interactive crafting loop
+            </expand>
+
+        2.  If <result/> is `DONE` or `CANCEL`, <break/>.
+
+        3.  Otherwise <result/> has the format `OTHER: <text/>`: set
+            <feature/> to <text/>, then directly craft it and report
+            it exactly as specified by the items 1 and 2 above
+            (including the CHANGELOG.md entry).
+
+        </while>
+        </if>
+
+    4.  Then *IMMEDIATELY* *STOP* all further skill processing. You
         *MUST* *NOT* output anything else in this STEP 4 or after it --
         *independent* of <ase-project-boxing/>, whose exposure rules
         are explicitly *overridden* here. Especially, do not output a
@@ -207,16 +241,16 @@ crafting actually demands, and you *MUST* *NOT* call
         `ase` MCP server and use the `text` field of its response for
         <timestamp-created/> and <timestamp-modified/> information. Then
         insert the current <ase-task-id/>, <timestamp-created/>,
-        <timestamp-modified/>, and <task-kind/> information and calculate
-        the number of words <words/> of <task-content/>.
+        <timestamp-modified/>, and <task-kind/> information.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`
+        MCP tool call only -- *NEVER* by executing a shell command.
 
     4.  Output a hint with the following <template/>:
 
         <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan created**
         </template>
 
     5.  Directly pass-through control to the next skill:

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

@@ -10,6 +10,7 @@
     [`--auto`|`-a`]
     [`--dry`|`-d`]
     [`--direct`|`-D`]
+    [`--interactive`|`-i`]
     [`--quick`|`-Q`]
     [`--next`|`-n` *option*[,...]]
     [*task-id*:] *feature*
@@ -51,6 +52,12 @@ entirely and applies the change set to the affected artifacts itself.
     `--next` have no effect, as neither approaches are proposed nor a
     plan is composed.
 
+`--interactive`|`-i`:
+    Craft *interactively*: implies `--direct` and, once the initial
+    *feature* has been applied, repeatedly asks for the *next change*
+    with a free-text dialog and immediately applies it in place, too,
+    until the user stops the loop by answering `DONE`.
+
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended feature approach, compose the plan *without* the
@@ -96,6 +103,12 @@ Craft a feature under a named task and directly hand off to implementation:
 ❯ /ase-code-craft --next IMPLEMENT auth: add JWT authentication middleware
 ```
 
+Craft interactively, applying one change after the other in place:
+
+```text
+❯ /ase-code-craft -i add a --verbose option to the CLI
+```
+
 ##  SEE ALSO
 
 [`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-task-edit`](../ase-task-edit/help.md),

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

@@ -169,7 +169,28 @@ Procedure
 3.  <step id="STEP 3: Detect Target Collisions"
         condition="<getopt-option-dry/> is not equal `true`">
 
-    1.  Determine the *existing worktrees* and *existing branches* by
+    1.  Determine the *worktree directory* of every part by calling the
+        `ase_worktree_path(id: "<part-id/>", create: true)` tool of the
+        `ase` MCP server once per <part-id/> of <parts/> and capturing
+        its output into the <part-dir/> of that part.
+
+        You *MUST* *NEVER* assemble such a path yourself, as only this
+        tool rejects a path leading through a symbolic link, through a
+        non-directory, or out of the repository -- a path both `git
+        worktree add` and `git worktree remove` would otherwise silently
+        follow and thereby write outside the repository.
+
+        <if condition="this tool call fails for any part">
+        Only output the following <template/> and then immediately *STOP*
+        processing the entire current skill, leaving the working copy and
+        *all* existing worktrees and branches untouched:
+
+        <template>
+        ⧉ **ASE**: ✪ skill: **ase-code-dissect**, ▶ ERROR: unsafe worktree directory -- cannot create worktrees
+        </template>
+        </if>
+
+    2.  Determine the *existing worktrees* and *existing branches* by
         running the corresponding commands (taken exactly as given) and
         capturing their outputs:
 
@@ -177,11 +198,11 @@ Procedure
 
         `git branch --list`
 
-    2.  Set <collisions/> to all <part-id/> of <parts/> for which either
-        a worktree directory `<repo-root/>/.ase/worktree/<part-id/>` or
-        a branch `<part-id/>` already exists.
+    3.  Set <collisions/> to all <part-id/> of <parts/> for which either
+        the worktree directory <part-dir/> or a branch `<part-id/>`
+        already exists.
 
-    3.  <if condition="<collisions/> is not empty AND <getopt-option-force/> is not equal `true`">
+    4.  <if condition="<collisions/> is not empty AND <getopt-option-force/> is not equal `true`">
         Only output the following <template/> -- with <collisions/>
         rendered as a comma-separated list of code spans -- and then
         immediately *STOP* processing the entire current skill, leaving
@@ -202,13 +223,13 @@ Procedure
         </ase-tpl-hint>
         </if>
 
-    4.  <if condition="<collisions/> is not empty AND <getopt-option-force/> is equal `true`">
+    5.  <if condition="<collisions/> is not empty AND <getopt-option-force/> is equal `true`">
         *Remove* every colliding target by running the corresponding
         commands (taken exactly as given) per colliding <part-id/>, and
         silently ignore the failure of an individual command when the
         corresponding worktree or branch does not exist:
 
-        `git worktree remove --force "<repo-root/>/.ase/worktree/<part-id/>"`
+        `git worktree remove --force "<part-dir/>"`
 
         `git worktree prune`
 
@@ -255,7 +276,7 @@ Procedure
             git-ignored, so the worktree itself never shows up as a
             change:
 
-            `git worktree add "<repo-root/>/.ase/worktree/<part-id/>"`
+            `git worktree add "<part-dir/>"`
 
             <if condition="this command fails">
             Only output the following <template/>, then *continue* with
@@ -270,7 +291,7 @@ Procedure
         4.  Apply the patch *inside* the freshly created worktree by
             running the corresponding command (taken exactly as given):
 
-            `git -C "<repo-root/>/.ase/worktree/<part-id/>" apply --whitespace=nowarn "<tmp-dir/>/ase-dissect-<part-id/>.patch"`
+            `git -C "<part-dir/>" apply --whitespace=nowarn "<tmp-dir/>/ase-dissect-<part-id/>.patch"`
 
             <if condition="this command fails">
             Only output the following <template/>, then *continue* with