@rse/ase 0.0.53 → 0.0.54

package/dst/ase-service.js

@@ -140,10 +140,10 @@ export class Service {
                 const n = Math.min(CHUNK, pos);
                 pos -= n;
                 fs.readSync(fd, buf, 0, n, pos);
-                tail = buf.toString("utf8", 0, n) + tail;
-                count = 0;
-                for (let i = 0; i < tail.length; i++)
-                    if (tail.charCodeAt(i) === 10)
+                const chunk = buf.toString("utf8", 0, n);
+                tail = chunk + tail;
+                for (let i = 0; i < chunk.length; i++)
+                    if (chunk.charCodeAt(i) === 10)
                         count++;
             }
             const all = tail.split("\n").filter((l) => l.length > 0);

package/dst/ase-setup.js

@@ -667,7 +667,7 @@ export default class SetupCommand {
         const devDflt = envDev !== "" && envDev !== "0" && envDev.toLowerCase() !== "false";
         /*  default for --tool derived from ASE_TOOL environment variable  */
         const envTool = process.env.ASE_TOOL ?? "";
-        const toolDflt = envTool !== "" ? envTool : "claude";
+        const toolDflt = envTool !== "" ? this.parseTool(envTool) : "claude";
         /*  register CLI top-level command "ase setup"  */
         const setupCmd = program
             .command("setup")

package/dst/ase-statusline.js

@@ -182,7 +182,7 @@ export default class StatuslineCommand {
     register(program) {
         /*  default for --tool derived from ASE_TOOL environment variable  */
         const envTool = process.env.ASE_TOOL ?? "";
-        const toolDflt = envTool !== "" ? envTool : "claude";
+        const toolDflt = envTool !== "" ? this.parseTool(envTool) : "claude";
         program
             .command("statusline")
             .description("Render Claude Code or GitHub Copilot CLI statusline from stdin JSON")

package/dst/ase-task.js

@@ -384,6 +384,7 @@ export class TaskMCP {
                 };
             }
         });
+        /*  task delete  */
         mcp.registerTool("ase_task_delete", {
             title: "ASE task delete",
             description: "Delete a previously persisted task by `id`. " +
@@ -396,8 +397,8 @@ export class TaskMCP {
             try {
                 const removed = Task.delete(args.id);
                 const msg = removed ?
-                    "OK: removed task" :
-                    "WARNING: task not found";
+                    `task_delete: OK: removed task "${args.id}"` :
+                    `task_delete: WARNING: no task "${args.id}" to remove`;
                 return {
                     content: [{ type: "text", text: msg }]
                 };
@@ -427,7 +428,7 @@ export class TaskMCP {
                 const renamed = Task.rename(args.old, args.new);
                 const msg = renamed ?
                     `task_rename: OK: renamed task "${args.old}" to "${args.new}"` :
-                    "WARNING: task not found";
+                    `task_rename: WARNING: no task "${args.old}" to rename`;
                 return {
                     content: [{ type: "text", text: msg }]
                 };

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.53",
+    "version":                              "0.0.54",
     "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.53",
+    "version":     "0.0.54",
     "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.53",
+    "version":     "0.0.54",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

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

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

@@ -5,7 +5,7 @@ description: Review software architecture, including package cohesion and inter-
 user-invocable: true
 disable-model-invocation: false
 model: opus
-effort: medium
+effort: high
 allowed-tools:
     - "Bash(wc:*)"
     - "Bash(ls:*)"

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

@@ -24,8 +24,10 @@ Discover Components
 Discover Components
 </skill>
 
+<role>
 Your role is an experienced, *expert-level software architect*,
 specialized in *finding components* (libraries/frameworks) for the technology stack.
+</role>
 
 <objective>
 *Discover* additional, *third-party components* (libraries/frameworks)

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

@@ -5,7 +5,7 @@ description: >
     Analyze the source code for problems in the logic and semantics and its related control flow.
 user-invocable: true
 disable-model-invocation: false
-effort: medium
+effort: high
 allowed-tools:
     - "Agent"
 ---

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

@@ -22,8 +22,10 @@ Explain Source Code
 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

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

@@ -5,7 +5,7 @@ description: >
     Give insights into the source code.
 user-invocable: true
 disable-model-invocation: false
-effort: low
+effort: medium
 allowed-tools:
     - "Bash(git)"
     - "Bash(sort)"
@@ -25,8 +25,10 @@ Project 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.

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

@@ -6,7 +6,7 @@ description: >
     Use when the user wants to "lint" or "check" source code.
 user-invocable: true
 disable-model-invocation: false
-effort: medium
+effort: high
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md

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

@@ -6,7 +6,7 @@ description: >
     Use when the user wants to "proofread" or "spellcheck" a document.
 user-invocable: true
 disable-model-invocation: false
-effort: medium
+effort: high
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md

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

@@ -8,7 +8,7 @@ disable-model-invocation: false
 effort: medium
 allowed-tools:
     - "Bash(git log *)"
-    - "Bash(git status *)"
+    - "Bash(git diff *)"
     - "Bash(git show *)"
     - "Write"
     - "Edit"
@@ -24,78 +24,149 @@ Update ChangeLog Entries
 Update ChangeLog Entries
 </skill>
 
+<role>
 Your role is an experienced, *expert-level software developer*,
 specialized in *Git version control*.
+</role>
 
 <objective>
-Help to complete, consolidate and sort *ChangeLog* entries,
-based on underlying *Git* commit messages.
+Help to complete, consolidate and sort *ChangeLog* entries of the most
+recent *ChangeLog* section, based on underlying *Git* commits and staged
+changes.
 </objective>
 
-For this, understand that ChangeLog entries are
-always formatted `<prefix/>: <summary/>` where
-the <prefix/> is one of the following tags
-and their usual related changes...
+Format
+------
 
-    -   `FEATURE`: new functionality or configuration
-    -   `IMPROVEMENT`: improved functionality or configuration
-    -   `BUGFIX`: corrected functionality or configuration
-    -   `UPDATE`: updated functionality or configuration
-    -   `CLEANUP`: cleaned up functionality or configuration
-    -   `REFACTOR`: refactored functionality or configuration
+The *ChangeLog* file is a Markdown formatted file named `CHANGELOG.md`,
+and contains sections with headers in the style `N.M.K (YYYY-MM-DD)`.
 
-...and <summary/> is not longer than about 60-80 characters.
-The ChangeLog entries for a single product release version
-are also grouped and sorted according to the above <prefix/>es.
+Each *ChangeLog* entry is always formatted as `<prefix/>: <summary/>`
+where the <prefix/> is one of the following tags and their usual related
+changes:
+
+    -   `FEATURE`:     new        functionality or configuration
+    -   `IMPROVEMENT`: improved   functionality or configuration
+    -   `BUGFIX`:      corrected  functionality or configuration
+    -   `UPDATE`:      updated    functionality or configuration
+    -   `CLEANUP`:     cleaned up functionality or configuration
+    -   `REFACTOR`:    refactored functionality or configuration
+
+The <summary/> is not longer than about 60-80 characters. The
+*ChangeLog* entries for a single product release version are also always
+grouped and sorted according to the above <prefix/> list.
+
+Processing
+----------
 
 <flow>
 
-1. <step id="STEP 1: Locate and read existing ChangeLog entries">
-   The *ChangeLog* file `CHANGELOG.md` contains sections
-   with headers in the style `N.M.K (YYYY-MM-DD)`.
-   The `CHANGELOG.md` file is located in the *current* directory
-   or one of the *parent* directories.
-   </step>
-
-2. <step id="STEP 2: Read corresponding Git commit log messages">
-   *Ignore* the current Git *index* and Git *stash* and use the Git *commits* only.
-   For finding the corresponding Git commits, use the `N.M.K`
-   from the *second* header in the *ChangeLog* file as
-   the corresponding Git tag and then check all Git commits
-   between `HEAD` and this tag.
-   </step>
-
-3. <step id="STEP 3: Complete ChangeLog entries">
-   Without immediately modifying the `CHANGELOG.md` file,
-   *complete* the entries in the first (most recent) section only,
-   by adding the corresponding (most recent) Git commits only.
-   For each Git commit, reduce the Git commit messages to a single
-   short sentence.
-   </step>
-
-4. <step id="STEP 4: Consolidate ChangeLog entries">
-   Without immediately modifying the `CHANGELOG.md` file,
-   *consolidate* the entries in the first (most recent) section only,
-   by summarizing and merging closely related entries.
-   Perform the entry consolidation per prefix group only.
-   If a changelog <summary/> is too short or is not comprehensible enough
-   because of too little context, add some context, especially references
-   to the class/module/package, etc.
-   </step>
-
-5. <step id="STEP 5: Sort ChangeLog entries">
-   Without immediately modifying the `CHANGELOG.md` file,
-   *sort* the entries in the first (most recent) section only.
-   Instead of the chronological commit order, group the entries
-   by the prefixes.
-   </step>
-
-6. <step id="STEP 6: Write modified ChangeLog entries">
-   Finally, *update* the `CHANGELOG.md` file with the
-   completed, consolidated and sorted *ChangeLog* entries.
-   Also, update the date `YYYY-MM-DD` in the `N.M.K (YYYY-MM-DD)`
-   headline of the *first* (most recent) section.
-   </step>
+1.  <step id="STEP 1: Locate and read ChangeLog entries">
+
+    The *ChangeLog* file `CHANGELOG.md` is located in the *current*
+    directory or one of the *parent* directories of the current project.
+    Locate and read this file. Store its relative path in <filename/>.
+
+    You *MUST* *NOT* output anything, except the result with the
+    following <template/>:
+
+    <template>
+    &#x1F535; **CHANGELOG FILE:** `<filename/>`
+    </template>
+
+    </step>
+
+2.  <step id="STEP 2: Determine artifact changes">
+
+    You *MUST* *NOT* output anything, except introduce the current
+    operation with an output based on the following <template/>:
+
+    <template>
+    &#x1F535; **DETERMINE ARTIFACT CHANGES:**
+    </template>
+
+    To update to entries of the most recent *ChangeLog* section, consult
+    the Git *commits* plus the currenly already staged changes in the Git
+    *index*, but *ignore* the Git *stash* and 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 staged Git *changes* in the Git
+    *index*, use the command `git diff --cached --numstat`, but silently
+    skip already existing changes to the `CHANGELOG.md` file itself. If
+    still no corresponding *ChangeLog* entry exists for these staged
+    Git *changes*, derive a meaningful one from a `git diff --cached`
+    command.
+
+    </step>
+
+3.  <step id="STEP 3: Complete ChangeLog entries">
+
+    You *MUST* *NOT* output anything, except introduce the current
+    operation with an output based on the following <template/>:
+
+    <template>
+    &#x1F535; **COMPLETE ENTRIES:**
+    </template>
+
+    Without immediately modifying the `CHANGELOG.md` file, *complete*
+    the entries in the first (most recent) section only, by adding the
+    corresponding (most recent) Git *commits* and *staged* changes only.
+
+    For each Git commit, reduce the Git commit messages to a single
+    short <summary/> sentence, not longer than 60-80 characters.
+
+    If a <summary/> is too short or especially is not comprehensible
+    enough because of too little context information, add some essential
+    context, especially references to the class/module/package, etc.
+    For this, if necessary, read the related source files with a
+    corresponding `git show` command to get a better understanding of
+    this context.
+
+    </step>
+
+4.  <step id="STEP 4: Consolidate and sort ChangeLog entries">
+
+    You *MUST* *NOT* output anything, except introduce the current
+    operation with an output based on the following <template/>:
+
+    <template>
+    &#x1F535; **CONSOLIDATE ENTRIES:**
+    </template>
+
+    Without immediately modifying the `CHANGELOG.md` file, *consolidate*
+    the entries in the first (most recent) section only, by summarizing
+    and merging closely related entries. Perform the entry consolidation
+    per <prefix/> group only.
+
+    Without immediately modifying the `CHANGELOG.md` file, *sort* the
+    entries in the first (most recent) section only. Instead of the
+    chronological commit order, group the entries by the <prefix/>es.
+
+    </step>
+
+5.  <step id="STEP 5: Write modified ChangeLog entries">
+
+    You *MUST* *NOT* output anything, except introduce the current
+    operation with an output based on the following <template/>:
+
+    <template>
+    &#x1F7E0; **UPDATING CHANGELOG:**
+    </template>
+
+    Finally, *update* the `CHANGELOG.md` file with the completed,
+    consolidated and sorted *ChangeLog* entries. Also, update the date
+    `YYYY-MM-DD` in the `N.M.K (YYYY-MM-DD)` header of the *first* (most
+    recent) section.
+
+    You *MUST* *NOT* output any further summary or give any further
+    explanations.
+
+    </step>
 
 </flow>
 

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

@@ -1,6 +1,5 @@
 ---
 name: ase-meta-commit
-argument-hint: ""
 description: >
     Determine commit message for staged Git changes.
 user-invocable: true
@@ -20,8 +19,10 @@ Git Commit
 Git Commit
 </skill>
 
+<role>
 Your role is an experienced, *expert-level software developer*,
 specialized in *Git commit messages*.
+</role>
 
 <objective>
 Help to *craft* a *concise commit message* for the
@@ -29,28 +30,34 @@ currently staged Git changes.
 </objective>
 
 <flow>
+
 1.  <step id="STEP 1: Find out staged changes">
-    Run the following command to find out details
-    of what changes are currently staged for commit:
 
-    `git diff --staged`
+    Run the following command to find out details of what changes are
+    currently staged in the Git *index* for commit:
+
+    `git diff --cached`
+
     </step>
 
 2.  <step id="STEP 2: Craft a consolidated commit message">
+
     Craft a commit <message/> in the following format:
 
     `<type/>: <summary/>`
 
     The known <type/>s and their usual corresponding kind of change are:
-    -   `FEATURE`: new functionality or configuration
+
+    -   `FEATURE`:     new functionality or configuration
     -   `IMPROVEMENT`: improved functionality or configuration
-    -   `BUGFIX`: corrected functionality or configuration
-    -   `UPDATE`: updated functionality or configuration
-    -   `CLEANUP`: cleaned up functionality or configuration
-    -   `REFACTOR`: refactored functionality or configuration
+    -   `BUGFIX`:      corrected functionality or configuration
+    -   `UPDATE`:      updated functionality or configuration
+    -   `CLEANUP`:     cleaned up functionality or configuration
+    -   `REFACTOR`:    refactored functionality or configuration
 
     The rules for generating <summary/> are:
-    -   Use a maximum of 70 characters
+
+    -   Use a maximum of 60-80 characters
     -   Use imperative mood ("add" not "added")
     -   Use *no* period at the end
     -   Use *no* Markdown formatting
@@ -63,6 +70,8 @@ currently staged Git changes.
     </template>
 
     Do *not* output any further explanation.
+
     </step>
+
 </flow>
 

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

@@ -10,6 +10,7 @@ description: >
     Use when user says "persona <persona>" or "be <persona>".
 user-invocable: true
 disable-model-invocation: false
+effort: medium
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md

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

@@ -88,7 +88,7 @@ by querying *multiple* AIs for an *optimal consensus*.
 3.  <step id="STEP 3: Summarize Responses">
 
     Agents which returned a response with an `ERROR:` prefix are
-    silently skipped and are treatd as not available.
+    silently skipped and are treated as not available.
 
     Summarize all responses, of both yourself and all available agents
     with just 1 to 7 corresponding bullet points and with short

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

@@ -79,7 +79,7 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
     calls above into a single response and output it without giving any
     further explanations.
 
-    For the consolidation, do *NOT* remove any orginal information,
+    For the consolidation, do *NOT* remove any original information,
     just *MERGE* all overlapping information.
 
     </step>

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

@@ -18,7 +18,9 @@ Five-Whys Root-Cause Analysis
 Five-Whys Root-Cause Analysis
 </skill>
 
+<role>
 Your role is an *expert-level assistant*.
+</role>
 
 <objective>
 Apply the *Five-Whys* *root-cause analysis* technique to investigate

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

@@ -20,7 +20,9 @@ Delete a Task Plan
 Delete a Task Plan
 </skill>
 
+<role>
 Your role is an experienced, *expert-level assistant*.
+</role>
 *Delete* the task plan.
 
 Procedure

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

@@ -30,9 +30,11 @@ Iteratively Edit a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *planning* of changes
 through *iterative conversational refinement*.
+</role>
 
 Establish and refine the *task plan* purely through a *chat-driven
 loop*. The user steers each round via interactive dialog that offers

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

@@ -28,8 +28,10 @@ Implement a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *implementation* of changes.
+</role>
 
 *Implement* the task plan by modifying the *artifacts*
 with a corresponding, complete *change set*.

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

@@ -28,8 +28,10 @@ Preflight a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *implementation* of changes.
+</role>
 
 *Preflight* the implementation of a task plan by creating a draft
 for a corresponding, *complete source code change set*.

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

@@ -7,7 +7,7 @@ description: >
     the "task", "plan", "spec", or "specification".
 user-invocable: true
 disable-model-invocation: false
-effort: xhigh
+effort: high
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -28,8 +28,10 @@ Reboot a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *planning* of changes.
+</role>
 
 *Reboot* the task plan by crafting it from scratch,
 based on the existing *WHAT* and *WHY*.

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

@@ -20,7 +20,10 @@ Rename a Task Plan
 Rename a Task Plan
 </skill>
 
+<role>
 Your role is an experienced, *expert-level assistant*.
+</role>
+
 *Rename* the task plan.
 
 Procedure

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

@@ -20,7 +20,9 @@ View a Task Plan
 View a Task Plan
 </skill>
 
+<role>
 Your role is an experienced, *expert-level assistant*.
+</role>
 *View* the task plan.
 
 Procedure

package/plugin/commands/ase-code-lint/complete.md

@@ -1,9 +0,0 @@
----
-argument-hint: ""
-description: "During Lint: Complete Code Change"
----
-
-Sorry, your last proposed code change set seems to be not really *complete*,
-as some code changes seem to be missing.
-Please *re-assess* and propose the *entire necessary change set*, all *at once*.
-

package/plugin/commands/ase-code-lint/explain.md

@@ -1,9 +0,0 @@
----
-argument-hint: "<issue>"
-description: "During Lint: Improve Explanation"
----
-
-I am still *musing* on your last proposed code change.
-$ARGUMENTS.
-Please *improve your explanation* and *propose it again*.
-

package/plugin/commands/ase-code-lint/nope.md

@@ -1,11 +0,0 @@
----
-argument-hint: ""
-description: "During Lint: Reject Change and Continue"
----
-
-I *reject* your last proposed code change.
-
-Do *NOT apply* your last code change to the code.
-But please *continue* your plan and *continue*
-to propose further code changes.
-

package/plugin/commands/ase-code-lint/reassess.md

@@ -1,15 +0,0 @@
----
-argument-hint: "<question>"
-description: "During Lint: Re-Assess Last Change"
----
-
-Are you *really sure*? $ARGUMENTS
-
-Please *re-assess* and *reason* on your last proposed code change!
-
-Then, if you are still sure that it is correct, please *propose the code
-change once again* before continuing with your plan.
-
-Otherwise, if you are unsure, be transparent and tell me your new
-reasoned concerns and continue with your plan immediately.
-

package/plugin/commands/ase-code-lint/recheck.md

@@ -1,9 +0,0 @@
----
-argument-hint: ""
-description: "During Lint: Recheck Change"
----
-
-The source code was *updated externally*.
-Please update your last code change against the latest source code
-and *propose the code change again* before you continue following your review.
-

package/plugin/commands/ase-code-lint/refine.md

@@ -1,9 +0,0 @@
----
-argument-hint: "<hint>"
-description: "During Lint: Refine Change"
----
-
-Please *refine* your last proposed code change: $ARGUMENTS.
-Then please propose the refined code change again before
-you continue following your review.
-