@rse/ase 0.0.52 → 0.0.54

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

@@ -52,7 +52,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 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 `task_save(...)`.
+permitted way to persist artifacts is via `ase_task_save(...)`.
 
 1.  **Reason About Refactoring**:
 
@@ -61,8 +61,8 @@ permitted way to persist artifacts is via `task_save(...)`.
         ">
         Set <ase-task-id><request/></ase-task-id> (set task id to request)
         and <request></request> (set request empty), call the
-        `task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
-        from the `ase` MCP service to switch the task, and then only
+        `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
+        from the `ase` MCP server to switch the task, and then only
         output the following <template/>:
 
         <template>
@@ -73,8 +73,8 @@ permitted way to persist artifacts is via `task_save(...)`.
     2.  If <request/> has the format `<id/>: <text/>` where <id/> matches
         the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
         <request><text/></request> and <ase-task-id><id/></ase-task-id>
-        and call the `task_id(id: <ase-task-id/>, session:
-        <ase-session-id/>)` tool from the `ase` MCP service to
+        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. Do not output anything.
 
     3.  If <request/> is empty,
@@ -91,8 +91,8 @@ permitted way to persist artifacts is via `task_save(...)`.
         ">
         Set <ase-task-id/> to a unique task id, derived from <request/>,
         which consists of two lower-case words concatenated with a
-        `-` character. Then call the `task_id(id: <ase-task-id/>,
-        session: <ase-session-id/>)` tool from the `ase` MCP service to
+        `-` character. Then call the `ase_task_id(id: <ase-task-id/>,
+        session: <ase-session-id/>)` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
         </if>
 
@@ -262,15 +262,15 @@ permitted way to persist artifacts is via `task_save(...)`.
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 
-    2.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP service and use the `text` field of its response for
+    2.  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
         <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/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `task_save(id: <ase-task-id/>, text: <content/>)`.
+        `ase_task_save(id: <ase-task-id/>, text: <content/>)`.
 
     4.  Output a hint with the following <template/>:
 

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

@@ -52,18 +52,18 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 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 `task_save(...)`.
+permitted way to persist artifacts is via `ase_task_save(...)`.
 
 1.  **Reason About Problem**:
 
     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 `task_id(id:
+        <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 service to implicitly switch the task, and then
-        call the `kv_get(key: "ase-issue-<problem-id/>")` tool of
-        the `ase` MCP service to retrieve the previously persisted
+        `ase` MCP server to implicitly switch the task, and 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.
@@ -73,8 +73,8 @@ permitted way to persist artifacts is via `task_save(...)`.
         ">
         Set <ase-task-id><problem/></ase-task-id> (set task id to problem)
         and <problem></problem> (set problem empty), call the
-        `task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
-        from the `ase` MCP service to switch the task, and then only
+        `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)` tool
+        from the `ase` MCP server to switch the task, and then only
         output the following <template/>:
 
         <template>
@@ -85,8 +85,8 @@ permitted way to persist artifacts is via `task_save(...)`.
     3.  If <problem/> has the format `<id/>: <text/>` where <id/> matches
         the regexp `^[a-zA-Z][a-zA-Z0-9_-]+$`, then set
         <problem><text/></problem> and <ase-task-id><id/></ase-task-id>
-        and call the `task_id(id: <ase-task-id/>, session:
-        <ase-session-id/>)` tool from the `ase` MCP service to
+        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. Do not output anything.
 
     4.  If <problem/> is empty,
@@ -103,8 +103,8 @@ permitted way to persist artifacts is via `task_save(...)`.
         ">
         Set <ase-task-id/> to a unique task id, derived from <problem/>,
         which consists of two lower-case words concatenated with a
-        `-` character. Then call the `task_id(id: <ase-task-id/>,
-        session: <ase-session-id/>)` tool from the `ase` MCP service to
+        `-` character. Then call the `ase_task_id(id: <ase-task-id/>,
+        session: <ase-session-id/>)` tool from the `ase` MCP server to
         implicitly switch the task. Do not output anything.
         </if>
 
@@ -310,21 +310,21 @@ permitted way to persist artifacts is via `task_save(...)`.
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
         filesystem-modifying tool during this step.
 
-    2.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP service and use the `text` field of its response for
+    2.  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
         <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/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `task_save(id: <ase-task-id/>, text: <content/>)`.
+        `ase_task_save(id: <ase-task-id/>, text: <content/>)`.
 
     4.  If <problem-id/> is set (i.e. the <problem/> was retrieved from
-        `kv_get` in STEP 1.3 via key `ase-issue-<problem-id/>`),
-        you *MUST* additionally call the `kv_delete(key:
+        `ase_kv_get` in STEP 1.3 via key `ase-issue-<problem-id/>`),
+        you *MUST* additionally call the `ase_kv_delete(key:
         "ase-issue-<problem-id/>")` tool of the `ase` MCP
-        service to remove the now-resolved analyzer result from the
+        server to remove the now-resolved analyzer result from the
         in-memory key/value store.
 
     5.  Output a hint with the following <template/>:

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
@@ -98,7 +98,7 @@ documents.
 
 3.  <step id="STEP 3: Correction">
 
-    1.  You *MUST* call the MCP tool `config_set(key: "agent.skill", val:
+    1.  You *MUST* call the MCP tool `ase_config_set(key: "agent.skill", val:
         "ase-docs-proofread", scope: "session:<ase-session-id/>")` of the
         `ase` MCP server.
 
@@ -202,7 +202,7 @@ documents.
 
         </for>
 
-    3.  You *MUST* call the MCP tool `config_delete(key: "agent.skill",
+    3.  You *MUST* call the MCP tool `ase_config_delete(key: "agent.skill",
         scope: "session:<ase-session-id/>")` of the `ase` MCP server.
 
     4.  You *MUST* *NOT* output any further additional explanations or

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-evaluate/SKILL.md

@@ -153,9 +153,9 @@ multi-*criteria* decision matrix.
         not output anything.
 
     -   Then, calculate the ratings <rating-K/> (K=1-N) for all
-        alternatives in a single call by invoking the `decision_matrix(matrix:
+        alternatives in a single call by invoking the `ase_decision_matrix(matrix:
         [ [ <weight-1/>, <eval-1-1/>, ..., <eval-1-N/> ], ..., [ <weight-M/>,
-        <eval-M-1/>, ..., <eval-M-N/> ] ])` tool of the `ase` MCP service.
+        <eval-M-1/>, ..., <eval-M-N/> ] ])` tool of the `ase` MCP server.
         The tool returns an array of N numerical values, where the K-th
         entry is the product-sum of all weights <weight-L/> (L=1-M) and
         the evaluation <eval-K-L/> (L=1-M) for alternative <alternative-K/>.

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
@@ -23,8 +24,8 @@ Persona Configuration
     Do not output anything.
 
 2.  <if condition="<request/> is empty">
-    1.  Call the `persona(session: <ase-session-id/>)`
-        tool from the `ase` MCP service and set
+    1.  Call the `ase_persona(session: <ase-session-id/>)`
+        tool from the `ase` MCP server and set
         <ase-persona-style/> to its `text` output.
         Do not output anything.
 
@@ -45,8 +46,8 @@ Persona Configuration
         </template>
 
     2.  Set <ase-persona-style><request/></ase-persona-style> and
-        call the `persona(style: <ase-persona-style/>, session:
-        <ase-session-id/>)` tool from the `ase` MCP service. Do not
+        call the `ase_persona(style: <ase-persona-style/>, session:
+        <ase-session-id/>)` tool from the `ase` MCP server. Do not
         output anything.
 
     3.  Output the following <template/>:

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
@@ -45,9 +47,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Perform Operation**:
 
-    1.  Call the `task_delete(id: <id/>)` tool of the `ase` MCP
-        service to delete the task plan content and set <text/> to the
-        `text` output field of this `task_delete` tool call. Do not
+    1.  Call the `ase_task_delete(id: <id/>)` tool of the `ase` MCP
+        server to delete the task plan content and set <text/> to the
+        `text` output field of this `ase_task_delete` tool call. Do not
         output anything related to this MCP tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
@@ -65,9 +67,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
     2.  <if condition="<id/> is equal <ase-task-id/> AND <ase-task-id/> is not equal 'default'">
-        Set <ase-task-id>default</ase-task-id>. Call the `task_id(id:
+        Set <ase-task-id>default</ase-task-id>. Call the `ase_task_id(id:
         <ase-task-id/>, session: <ase-session-id/>)` tool from the `ase`
-        MCP service to switch the task to the default task. Only output
+        MCP server to switch the task to the default task. Only output
         the following <template/>:
 
         <template>