@rse/ase 0.0.57 → 0.0.58

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.0.57",
+    "version":                              "0.0.58",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

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

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

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

package/plugin/meta/ase-getopt.md

@@ -10,14 +10,27 @@ set placeholders into the context as a side-effect.
 1.  **Determine Parameters**:
     Set <getopt-skill><arg1/></getopt-skill>.
     Set <getopt-spec>--help|-h <arg2/></getopt-spec>.
-    Set <getopt-opts><arg3/></getopt-opts>.
     Set <getopt-args><content/></getopt-args>.
 
-2.  **Short-Circuit for Quick Processing**:
-    If <getopt-opts/> contains `quick` *AND*
-    <getopt-args/> does *NOT* match the regexp `^\s*-`:
-    Set <getopt-arguments><getopt-args/></getopt-arguments> and
-    then just silently *SKIP* the following steps 3-7!
+2.  **Short-Circuit Processing**:
+    If <getopt-args/> does *NOT* match the regexp `(^|\s)-` (i.e.
+    contains no options at all):
+
+    For each option token in <getopt-spec/> of the form
+    `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)]`, set
+    <getopt-option-<long/>/> to <default/> (for `=<default/>`
+    form), or to <c1/> (the first choice, for `=(<c1/>|<c2>/|...)`
+    form), or to `false` (for value-less options). Then set
+    <getopt-arguments><getopt-args/></getopt-arguments>.
+
+    Additionally, simulate <getopt-info/> as a comma-separated
+    markdown rendering of the parsed options in the form `<longN/>:
+    **<valueN/>**, [...]` (joined with `, `, with each value
+    shell-quoted if value contains spaces or special characters, and
+    excluding the `help` option).
+
+    Then silently *SKIP* only the following steps 3-6
+    and proceed directly to step 7 to display the results.
 
 3.  **MCP Call**:
     Call the `ase_getopt(name: "<getopt-skill/>", spec:

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.0.57",
+    "version":                              "0.0.58",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-craft
-argument-hint: "[--help|-h] [--auto|-a] [--next|-n <option>] [<task-id>:] <feature>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--next|-n <option>] [<task-id>:] <feature>"
 description: >
     Craft Source Code:
     Use when user wants to create or craft a new feature from scratch.
@@ -23,7 +23,7 @@ Craft Source Code
 
 <expand name="getopt"
     arg1="ase-code-craft"
-    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    arg2="--auto|-a --dry|-d --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
     $ARGUMENTS
 </expand>
 
@@ -261,6 +261,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         the information from feature A<n/> and all derived realization
         decisions into it. Store the resulting task plan in <content/>.
 
+        If a `CHANGELOG.md` file exists in the project (or in any
+        affected sub-package), the plan *MUST* include, as part of its
+        `## ※ CHANGES` section, an explicit bullet point describing
+        the addition of a corresponding new entry to that `CHANGELOG.md`
+        file, aligned with its existing style and conventions.
+
+        <if condition="<getopt-option-dry/> is equal `true`">
+        You *MUST* completely omit the `## ※ VERIFICATION` section
+        (including its heading and all of its bullet points) from
+        <content/>.
+        </if>
+
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 

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

@@ -8,6 +8,7 @@
 `ase-code-craft`
     [`--help`|`-h`]
     [`--auto`|`-a`]
+    [`--dry`|`-d`]
     [`--next`|`-n` *option*]
     [*task-id*:] *feature*
 
@@ -31,6 +32,13 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     Automatically pick the recommended feature approach without
     asking the user via the interactive dialog.
 
+`--dry`|`-d`:
+    Compose the plan *without* the `※ VERIFICATION` section. When
+    `ase-task-implement` later applies such a plan, it strictly skips
+    the entire verification phase (no build, tests, linter,
+    type-checker, or program execution) once the source files have
+    been modified.
+
 `--next`|`-n` *option*:
     Automatically choose the next step after composing the plan,
     where *option* is either `none` (default, hand-off to

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-refactor
-argument-hint: "[--help|-h] [--auto|-a] [--next|-n <option>] [<task-id>:] <request>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--next|-n <option>] [<task-id>:] <request>"
 description: >
     Refactor Code Base:
     Use when user wants to refactor the code base.
@@ -23,7 +23,7 @@ Refactor Artifacts
 
 <expand name="getopt"
     arg1="ase-code-refactor"
-    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    arg2="--auto|-a --dry|-d --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
     $ARGUMENTS
 </expand>
 
@@ -252,6 +252,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         the information from refactoring A<n/> and all derived realization
         decisions into it. Store the resulting task plan in <content/>.
 
+        If a `CHANGELOG.md` file exists in the project (or in any
+        affected sub-package), the plan *MUST* include, as part of its
+        `## ※ CHANGES` section, an explicit bullet point describing
+        the addition of a corresponding new entry to that `CHANGELOG.md`
+        file, aligned with its existing style and conventions.
+
+        <if condition="<getopt-option-dry/> is equal `true`">
+        You *MUST* completely omit the `## ※ VERIFICATION` section
+        (including its heading and all of its bullet points) from
+        <content/>.
+        </if>
+
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 

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

@@ -8,6 +8,7 @@
 `ase-code-refactor`
     [`--help`|`-h`]
     [`--auto`|`-a`]
+    [`--dry`|`-d`]
     [`--next`|`-n` *option*]
     [*task-id*:] *request*
 
@@ -31,6 +32,13 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     Automatically pick the recommended refactoring approach without
     asking the user via the interactive dialog.
 
+`--dry`|`-d`:
+    Compose the plan *without* the `※ VERIFICATION` section. When
+    `ase-task-implement` later applies such a plan, it strictly skips
+    the entire verification phase (no build, tests, linter,
+    type-checker, or program execution) once the source files have
+    been modified.
+
 `--next`|`-n` *option*:
     Automatically choose the next step after composing the plan,
     where *option* is either `none` (default, hand-off to

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

@@ -1,6 +1,6 @@
 ---
 name: ase-code-resolve
-argument-hint: "[--help|-h] [--auto|-a] [--next|-n <option>] [<task-id>:] <problem>"
+argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--next|-n <option>] [<task-id>:] <problem>"
 description: >
     Resolve Problem:
     Use when user wants a bug fixed or problem resolved.
@@ -23,7 +23,7 @@ Resolve Problem
 
 <expand name="getopt"
     arg1="ase-code-resolve"
-    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    arg2="--auto|-a --dry|-d --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
     $ARGUMENTS
 </expand>
 
@@ -300,6 +300,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         the success of the resolution, by using the <format/> defined for a
         task plan. Store the resulting task plan in <content/>.
 
+        If a `CHANGELOG.md` file exists in the project (or in any
+        affected sub-package), the plan *MUST* include, as part of its
+        `## ※ CHANGES` section, an explicit bullet point describing
+        the addition of a corresponding new entry to that `CHANGELOG.md`
+        file, aligned with its existing style and conventions.
+
+        <if condition="<getopt-option-dry/> is equal `true`">
+        You *MUST* completely omit the `## ※ VERIFICATION` section
+        (including its heading and all of its bullet points) from
+        <content/>.
+        </if>
+
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 

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

@@ -8,6 +8,7 @@
 `ase-code-resolve`
     [`--help`|`-h`]
     [`--auto`|`-a`]
+    [`--dry`|`-d`]
     [`--next`|`-n` *option*]
     [*task-id*:] *problem*
 
@@ -36,6 +37,13 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     Automatically pick the recommended resolution approach without
     asking the user via the interactive dialog.
 
+`--dry`|`-d`:
+    Compose the plan *without* the `※ VERIFICATION` section. When
+    `ase-task-implement` later applies such a plan, it strictly skips
+    the entire verification phase (no build, tests, linter,
+    type-checker, or program execution) once the source files have
+    been modified.
+
 `--next`|`-n` *option*:
     Automatically choose the next step after composing the plan,
     where *option* is either `none` (default, hand-off to

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-edit
-argument-hint: "[--help|-h] [--plan|-p <option>] [--next|-n <option>] [<id> | <id>: <instruction> | <instruction>]"
+argument-hint: "[--help|-h] [--plan|-p <option>] [--dry|-d] [--next|-n <option>] [<id> | <id>: <instruction> | <instruction>]"
 description: >
     Iteratively edit and refine a named plan for a task through a
     conversational loop. Each round, the current plan is shown and the
@@ -23,7 +23,7 @@ Iteratively Edit a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-edit"
-    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --next|-n=(none|DONE|IMPLEMENT|PREFLIGHT|REFINE)">
+    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --dry|-d --next|-n=(none|DONE|IMPLEMENT|PREFLIGHT|REFINE)">
     $ARGUMENTS
 </expand>
 
@@ -45,6 +45,47 @@ You *MUST* not skip any numbered item during processing!
 You *MUST* *NOT* output anything in this entire procedure, *except* when
 explicitly requested by this procedure via outputs based on a <template/>!
 
+<define name="apply-refinement">
+Treat the <instruction/> as a *refinement instruction* for
+the plan, and update <content/> in-place by *applying* the
+requested <instruction/> to the *plan*. When refining the
+plan this way, preserve the overall structure of the plan
+and only modify what the user actually requested. Do *not*
+rewrite unrelated sections of the plan.
+
+Calculate the number of words <words/> of <content/>.
+Set <content-dirty>true</content-dirty>.
+</define>
+
+<define name="generate-plan">
+Create a new plan from scratch and store the result as
+<content/> by closely following the defined plan format
+<format/> and injecting into it all the information from
+the <instruction/> and all decisions you derived from the
+<instruction/>.
+
+If a `CHANGELOG.md` file exists in the project (or in any
+affected sub-package), the plan *MUST* include, as part of
+its `## ※ CHANGES` section, an explicit bullet point
+describing the addition of a corresponding new entry to
+that `CHANGELOG.md` file, aligned with its existing style
+and conventions.
+
+<if condition="<getopt-option-dry/> is equal `true`">
+You *MUST* completely omit the `## ※ VERIFICATION` section
+(including its heading and all of its bullet points) from
+<content/>.
+</if>
+
+Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+`ase` MCP server and use the `text` field of its response
+for fresh <timestamp-created/> and <timestamp-modified/>
+information. Then insert the current <ase-task-id/>,
+<timestamp-created/>, and <timestamp-modified/> information
+and calculate the number of words <words/> of <content/>.
+Set <content-dirty>true</content-dirty>.
+</define>
+
 1.  **Determine Task and Instruction:**
 
     1.  Set <instruction><getopt-arguments/></instruction> initially.
@@ -194,19 +235,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         -   If <result/> is `OVERWRITE`:
 
-            Create a new plan from scratch and store the result as
-            <content/> by closely following the defined plan format
-            <format/> and injecting into it all the information from
-            the <instruction/> and all decisions you derived from the
-            <instruction/>.
-
-            Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-            `ase` MCP server and use the `text` field of its response
-            for fresh <timestamp-created/> and <timestamp-modified/>
-            information. Then insert the current <ase-task-id/>,
-            <timestamp-created/>, and <timestamp-modified/> information
-            and calculate the number of words <words/> of <content/>.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="generate-plan"/>
 
             Only output the following <template/> and continue processing:
 
@@ -217,15 +246,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         -   If <result/> is `REFINE`:
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-
-            Calculate the number of words <words/> of <content/>.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Only output the following <template/> and continue processing:
 
@@ -239,15 +260,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             Set <instruction><instruction/> <text/></instruction> (append
             the user's free-text hint to the existing instruction).
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-
-            Calculate the number of words <words/> of <content/>.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Only output the following <template/> and continue processing:
 
@@ -265,19 +278,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </if>
 
     5.  <if condition="<content/> is empty AND <instruction/> is not empty">
-        Create a new plan from scratch and store the result as
-        <content/> by closely following the defined plan format
-        <format/> and injecting into it all the information from
-        the <instruction/> and all decisions you derived from the
-        <instruction/>.
-
-        Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP server and use the `text` field of its response
-        for fresh <timestamp-created/> and <timestamp-modified/>
-        information. Then insert the current <ase-task-id/>,
-        <timestamp-created/>, and <timestamp-modified/> information
-        and calculate the number of words <words/> of <content/>.
-        Set <content-dirty>true</content-dirty>.
+        <expand name="generate-plan"/>
 
         Only output the following <template/> and continue processing:
 
@@ -398,13 +399,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             your instruction for further refining the plan?**`. Then set
             <instruction/> to the response of the user.
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Finally, only output the following <template/> and then
             *continue* the *loop* at step **3.1**!
@@ -417,13 +412,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
             Set <instruction><text/></instruction> (replace existing instruction).
 
-            Treat the <instruction/> as a *refinement instruction* for
-            the plan, and update <content/> in-place by *applying* the
-            requested <instruction/> to the *plan*. When refining the
-            plan this way, preserve the overall structure of the plan
-            and only modify what the user actually requested. Do *not*
-            rewrite unrelated sections of the plan.
-            Set <content-dirty>true</content-dirty>.
+            <expand name="apply-refinement"/>
 
             Finally, only output the following <template/> and then
             *continue* the *loop* at step **3.1**!

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

@@ -8,6 +8,7 @@
 `ase-task-edit`
     [`--help`|`-h`]
     [`--plan`|`-p` *option*]
+    [`--dry`|`-d`]
     [`--next`|`-n` *option*]
     [*id* | *id*: *instruction* | *instruction*]
 
@@ -32,6 +33,14 @@ command from outside the agent tool.
     *instruction*), or `PRESERVE` (preserve the existing plan by
     ignoring *instruction* and stopping skill processing).
 
+`--dry`|`-d`:
+    Generate any *new* plan *without* the `※ VERIFICATION` section.
+    Applies only to freshly generated plans, not to existing plans
+    loaded from disk. When `ase-task-implement` later applies such
+    a plan, it strictly skips the entire verification phase (no
+    build, tests, linter, type-checker, or program execution) once
+    the source files have been modified.
+
 `--next`|`-n` *option*:
     Automatically answer the user dialog for the next step (at the end
     of this skill) with *option*, which can be either `none` (default,

package/plugin/skills/ase-task-implement/SKILL.md

@@ -129,6 +129,16 @@ explicitly requested by this procedure via outputs based on a <template/>!
         overrules the implementation draft in the `IMPLEMENTATION DRAFT`
         section of <content/>.
 
+        <if condition="<content/> does NOT contain a `## ※ VERIFICATION` section heading">
+        The task plan deliberately *omits* the `## ※ VERIFICATION`
+        section. You *MUST* therefore *strictly skip* the entire
+        verification phase after modifying the source files: do *NOT*
+        run any build, do *NOT* run any tests, do *NOT* run any linter,
+        do *NOT* run any type-checker, do *NOT* execute the modified
+        program, and do *NOT* otherwise verify the change set in any
+        way.
+        </if>
+
     2.  Only output the following <template/>:
 
         <template>

package/plugin/skills/ase-task-implement/help.md

@@ -19,6 +19,13 @@ complete *change set*. The plan is loaded from
 section produced by `ase-task-preflight` is used as a hint — the
 plain plan content always overrules the draft.
 
+If the task plan deliberately *omits* the `※ VERIFICATION` section
+(as produced by `ase-code-craft`, `ase-code-refactor`,
+`ase-code-resolve`, or `ase-task-edit` when invoked with `--dry`),
+the entire verification phase is strictly skipped: no build, tests,
+linter, type-checker, or program execution is performed once the
+source files have been modified.
+
 After implementation, the user is asked whether to preserve or
 delete the task plan, unless `--next` pre-selects this choice.