@rse/ase 0.0.44 → 0.0.48

package/plugin/meta/ase-plan.md

@@ -51,7 +51,7 @@ You *MUST* honor the following hints on this *task plan* format:
 -   The <timestamp-created/> is the timestamp when this feature
     crafting specification was created. The
     <timestamp-modified/> is the timestamp when this feature
-    specification was last modified. Both use a ISO-style format
+    specification was last modified. Both use an ISO-style format
     value. The value of both can be determined by
     a call to the `timestamp(format: "yyyy-LL-dd HH:mm")`
     tool of the `ase` MCP service and use the `text` field of
@@ -61,10 +61,10 @@ You *MUST* honor the following hints on this *task plan* format:
     50 characters.
 
 -   The sections `※ CHANGES` and `※ VERIFICATION` all are just a short
-    list of 1-5 bullet points. Each bullet points is formatted as
+    list of 1-5 bullet points. Each bullet point is formatted as
     `- **<aspect/>**: <specification/>` where <aspect/> indicates
     the aspect of the section and <specification/> is 1-3 sentences
-    giving a *ultra precise* but also *ultra brief* and *ultra concise*
+    giving an *ultra precise* but also *ultra brief* and *ultra concise*
     description of the aspect.
 
 -   In all sections, break all lines with a newline character

package/plugin/meta/ase-skill.md

@@ -15,7 +15,7 @@ Skill Output
 -   *IMPORTANT*: *All* output is *exclusively* requested through
     <template/> sections. You *MUST* *NOT* output anything *EXCEPT* it
     is explicitly included in such a <template/> section. Especially,
-    you *MUST* *NOT* output any explanations on your own, except
+    you *MUST* *NOT* output any explanations on your own, unless
     explicitly requested.
 
 -   *IMPORTANT*: You *MUST* output all <template/> sections *EXACTLY* as provided
@@ -49,7 +49,7 @@ Skill Output
         padding, draw the top edge to that width, then keep every
         inner line (including annotations like `!`, `?`, `*`)
         within it. Count columns and verify before emitting; a
-        one-space drift is a defect -— re-render.
+        one-space drift is a defect — re-render.
 
 -   *IMPORTANT*: For *Findings* (problems, tradeoffs, warnings
     emitted by analysis skills):

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

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

@@ -170,7 +170,7 @@ interface quality, quality attributes, and architecture governance.
       races and shared mutable state is covered by SA17.)
     - **SA09 COHESION**: *strong cohesion* within each component —
       internal parts (functions, fields, methods) are *tightly
-      related*, *co-change*, and share data or behaviour; scattered
+      related*, *co-change*, and share data or behavior; scattered
       helpers that merely coexist by accident are flagged.
     - **SA10 EXTENSIBILITY**: components are *open for extension*
       (plugins, SPIs, hooks) but *closed for modification*.
@@ -266,7 +266,7 @@ interface quality, quality attributes, and architecture governance.
 
     - *Package-graph construction (SA19–SA21)*: parse each file's
       import (or equivalent language construct) statement, keep
-      only first-party packages within the analysed scope, and
+      only first-party packages within the analyzed scope, and
       persist two intermediate structures: the per-package
       incoming/outgoing class-edge map (drives SA20, SA21) and
       the per-package noun-token frequency table extracted from

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

@@ -9,6 +9,7 @@ disable-model-invocation: false
 effort: medium
 allowed-tools:
     - "Bash(npm search --json *)"
+    - "Bash(curl -s https://search.maven.org/*)"
     - "Skill"
     - "Agent"
 ---
@@ -92,7 +93,7 @@ for the technology stack to *provide* the *needed functionality*
         official package name as <package-K/>, the latest version as
         <version-K/>, the stars as <stars-K/>, the created date as
         <created-K/>, the last updated date as <updated-K/>, the total
-        number of downloads in the last month is <downloads-K/>.
+        number of downloads in the last month as <downloads-K/>.
 
     -   If <stack/> is "JavaScript" or "TypeScript":
 
@@ -114,9 +115,19 @@ for the technology stack to *provide* the *needed functionality*
 
         -   Based on the essential keywords <keyword-L/> (L=1-M),
             use the `ase-meta-search` skill in a subagent to *generally*
-            discover an initial set of a maximum of 12 *Java packages*
+            discover an initial set of a maximum of 12 *Maven packages*
             <component-K/> and at least their real name <name-K/> and
-            their unique package names <package-K/>.
+            their unique Maven coordinates <package-K/> of the form
+            `groupId:artifactId`.
+
+        -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+<keyword-M/>&rows=12&wt=json'`
+            to *specifically* discover an additional set of a maximum
+            of 12 *Maven packages* <component-K/> and at least their
+            unique Maven coordinates <package-K/> (i.e. `<g/>:<a/>` from
+            each result document's `g` and `a` fields), based on the
+            essential keywords <keyword-L/> (L=1-M). Merge the results
+            into the already existing result set, but deduplicate
+            entries by Maven coordinate.
 
     -   Call the `component_info(stack: <stack/>, components:
         [ <package-1/>, ..., <package-N/> ])` tool of the `ase` MCP

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

@@ -107,7 +107,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     7.  Ask the user for clarification if the goal of this crafting is too
         unclear.
 
-    8.  Do not output anything in this step, except you asked the user.
+    8.  Do not output anything in this step, unless you asked the user.
 
 2.  **Investigate Code Base**:
 
@@ -127,7 +127,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     1.  Generic Tenets:
 
         -   **Separation of Concerns**:
-            Clearly separate all individual concerns as good as possible.
+            Clearly separate all individual concerns as well as possible.
 
         -   **Code Base Alignment**:
             Strictly align with the existing source code base by exactly
@@ -162,7 +162,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             to change.
 
         -   **Loose Coupling, High Cohesion**:
-            Strike for good modularity by a set of small, focused parts
+            Strive for good modularity by a set of small, focused parts
             (high cohesion), connected by thin, explicit wires and
             interfaces (loose coupling).
 
@@ -229,7 +229,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             a *separate* `ase-meta-diagram` invocation and stack the
             rendered blocks *vertically* (labels `**Before:**` /
             `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situation.
+            entirely for simple or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

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

@@ -27,7 +27,7 @@ specialized in *explaining source code*.
 
 <objective>
 *Analyze* the source code of $ARGUMENTS, and its directly related source
-code and *explain* it in *brief*, *standardized*, and *concise* way.
+code and *explain* it in a *brief*, *standardized*, and *concise* way.
 </objective>
 
 <flow>

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

@@ -64,7 +64,7 @@ Give *insights* into the project through the source code of $ARGUMENTS.
     </step>
 
 3.  <step id="STEP 3: SOURCE CHURN">
-    Display the source files with caused the most churn by
+    Display the source files which caused the most churn by
     figuring out which source files have the most commits.
     Display the following <template/>:
 

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

@@ -37,7 +37,7 @@ related to a set of code quality aspects.
     </template>
 
     Then decide whether you detected *potential problems* which
-    *requires* a *code change* and *think* about this decision to be
+    *require* a *code change* and *think* about this decision to be
     sure it is *not* a false positive. Then choose one of the following
     cases:
 
@@ -87,7 +87,7 @@ related to a set of code quality aspects.
 2.  <step id="A01 - FORMATTING">
     <expand name="linter" arg1="A01 - FORMATTING">
     Check for inconsistently formatted code and badly vertically
-    aligned code on sub-sequent lines.
+    aligned code on subsequent lines.
 
     For vertical alignment, prefer to align on operators. For
     continuous code blocks (those without any blank lines at all),
@@ -135,7 +135,7 @@ related to a set of code quality aspects.
     Check for extremely long functions, and deeply nested code
     constructs.
 
-    Especially, for functions prefer fewer then 100 lines, and for
+    Especially, for functions prefer fewer than 100 lines, and for
     nested constructs prefer fewer than 10 nesting levels.
     </expand>
     </step>
@@ -183,11 +183,11 @@ related to a set of code quality aspects.
     </expand>
     </step>
 
-9.  <step id="A08 - COMPLICATENESS">
-    <expand name="linter" arg1="A08 - COMPLICATENESS">
+9.  <step id="A08 - COMPLICATEDNESS">
+    <expand name="linter" arg1="A08 - COMPLICATEDNESS">
     Check for complicated or cumbersome code constructs.
 
-    Especially, check for unnecessary difficult code constructs
+    Especially, check for unnecessarily difficult code constructs
     for which simpler solutions exist.
     </expand>
     </step>
@@ -196,9 +196,9 @@ related to a set of code quality aspects.
     <expand name="linter" arg1="A09 - CONCISENESS">
     Check for non-concise and boilerplate-based code.
 
-    Especially, check for unnecessary long code constructs for
+    Especially, check for unnecessarily long code constructs for
     which shorter solutions exist, and check for unnecessary
-    technical/infrastructural code with too less domain-specific
+    technical/infrastructural code with too few domain-specific
     aspects.
     </expand>
     </step>

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

@@ -107,7 +107,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     7.  Ask the user for clarification if the goal of this refactoring is
         too unclear.
 
-    8.  Do not output anything in this step, except you asked the user.
+    8.  Do not output anything in this step, unless you asked the user.
 
 2.  **Investigate Code Base**:
 
@@ -127,7 +127,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     1.  Generic Tenets:
 
         -   **Separation of Concerns**:
-            Clearly separate all individual concerns as good as possible.
+            Clearly separate all individual concerns as well as possible.
 
         -   **Code Base Alignment**:
             Strictly align with the existing source code base by exactly
@@ -155,7 +155,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             to change.
 
         -   **Loose Coupling, High Cohesion**:
-            Strike for good modularity by a set of small, focused parts
+            Strive for good modularity by a set of small, focused parts
             (high cohesion), connected by thin, explicit wires and
             interfaces (loose coupling).
 
@@ -219,7 +219,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             a *separate* `ase-meta-diagram` invocation and stack the
             rendered blocks *vertically* (labels `**Before:**` /
             `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situation.
+            entirely for simple or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

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

@@ -119,7 +119,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     8.  Ask the user for clarification if the goal of this resolution is
         too unclear.
 
-    9.  Do not output anything in this step, except you asked the user.
+    9.  Do not output anything in this step, unless you asked the user.
 
     10. Investigate and *figure out details* related to this problem.
         Report those details with the following <template/>:
@@ -155,7 +155,7 @@ permitted way to persist artifacts is via `task_save(...)`.
           `erDiagram`, depending on intent) and invoking the
           `ase-meta-diagram` skill by calling the tool `Skill(skill:
           "ase:ase-meta-diagram", args: <mermaid-spec/>)`. Omit
-          <optional-diagram/> entirely for simple or purely local situation.
+          <optional-diagram/> entirely for simple or purely local situations.
 
 2.  **Investigate Code Base**:
 
@@ -175,7 +175,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     1.  Generic Tenets:
 
         -   **Separation of Concerns**:
-            Clearly separate all individual concerns as good as possible.
+            Clearly separate all individual concerns as well as possible.
 
         -   **Code Base Alignment**:
             Strictly align with the existing source code base by exactly
@@ -189,7 +189,7 @@ permitted way to persist artifacts is via `task_save(...)`.
 
         -   **No Cleanups**:
             Strictly focus on resolving the problem and do not mix this
-            task with any other necessary code cleanups, except they are
+            task with any other necessary code cleanups, unless they are
             really necessary for resolving the task.
 
         -   **Minimum Flags**:
@@ -206,8 +206,8 @@ permitted way to persist artifacts is via `task_save(...)`.
         -   **Origin Proximity**:
             Problems for *obvious, particular, or expected* errors
             *should* be handled *near the origin*. Problems for
-            *theoretical, fictive, or unexpected* errors, *should* be
-            handled more general and in parent scopes.
+            *theoretical, fictive, or unexpected* errors *should* be
+            handled more generally and in parent scopes.
 
 4.  **Find Problem Resolution Approaches**:
 
@@ -265,7 +265,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             a *separate* `ase-meta-diagram` invocation and stack the
             rendered blocks *vertically* (labels `**Before:**` /
             `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situation.
+            entirely for simple or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

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

@@ -0,0 +1,293 @@
+---
+name: ase-docs-proofread
+argument-hint: "<docs-reference>"
+description: >
+    Analyze the documents for spelling, punctuation, or grammar errors.
+    Use when the user wants to "proofread" or "spellcheck" a document.
+user-invocable: true
+disable-model-invocation: false
+effort: medium
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
+
+Proofread Documentation
+=======================
+
+<skill name="ase-docs-proofread">
+Analyze the documents for spelling, punctuation, or grammar errors.
+</skill>
+
+<expand name="getopt"
+    arg1="ase-docs-proofread"
+    arg2="--auto|-a">
+    $ARGUMENTS
+</expand>
+
+<role>
+Your role is an experienced, *expert-level proofreader*, specialized in
+checking and correcting the *spelling*, *punctuation* and *grammar* of
+documents.
+</role>
+
+<objective>
+*Analyze* the documents of `<getopt-arguments/>` for problems in their
+*spelling*, *punctuation*, or *grammar* and propose corrections.
+</objective>
+
+<flow>
+
+1.  <step id="STEP 1: Investigation">
+
+    First, use the following <template/> to give a hint on this step:
+
+    <template>
+    &#x26AA; **PROOFREADING INVESTIGATION**
+    </template>
+
+    Then dispatch the investigation to a *sub-agent* via the `Agent`
+    tool so that *no* investigation details leak into the user-visible
+    transcript. The sub-agent performs the silent reading and checking;
+    only its final structured return value is consumed here.
+
+    Invoke the `Agent` tool *exactly once* with:
+
+    -   `subagent_type`: `general-purpose`
+    -   `description`: `Proofread Investigation`
+    -   `prompt`: a *self-contained* briefing, instructing the sub-agent to:
+
+        1.  Use the `Read` tool to read all document files referenced
+            by <getopt-arguments/>.
+
+        2.  Check the contained texts *only* for the following problem
+            types:
+
+            - **Spelling**
+            - **Punctuation**
+            - **Grammar**
+
+            Do *NOT* flag stylistic preferences, Markdown formatting
+            choices, code/identifiers, XML/template tags, technical
+            terms, intentional capitalization, list/heading style, or
+            anything inside fenced code blocks or backtick spans. Be
+            conservative — only report clear, objective errors.
+
+            For each found problem:
+
+            -   Set <type/> to the string `SPELLING`, `PUNCTUATION`, or
+                `GRAMMAR`, indicating the problem type.
+
+            -   Set <file/> to the *relative* filename path of the document.
+                Set <line/> to the numeric 1-based line number in the
+                document.
+
+            -   Set <old-text/> to the lines of the old text which
+                should be changed. Set <new-text/> to the lines of the
+                new text which will be changed.
+
+            -   Set <description/> to an ultra-brief and concise
+                Markdown-formatted description of the problem with
+                a hint of what is wrong and why it is wrong. In
+                this description, mark up all referenced verbatim
+                words <words/> from <old-text/> or <new-text/> as
+                quoted strings containing monospaced text with
+                Markdown based on the following <template/>:
+                <template>"`<words/>`"</template>.
+
+            -   Set <context-before/> to exactly *up to two* lines of
+                *unchanged* text context which occurs in the document
+                directly *before* <old-text/>, i.e., the lines (<line/> -
+                2) and (<line/> - 1). Reduce to just one line (<line/> -
+                1) if <old-text/> is the second line of the document. Set
+                <context-before/> to empty if <old-text/> is the first line in
+                the document.
+
+            -   Set <context-after/> to exactly *up to two* lines of
+                *unchanged* text content which occurs in the document
+                directly *after* <old-text/> the lines (<line/> + <n/> + 1)
+                and (<line/> + <n/> + 2), where <n/> is the number of lines
+                in <old-text/>. Reduce to just one line (<line/> + <n/> + 1)
+                if <old-text/> is the second-last line of the document. Set
+                <context-after/> to empty if <old-text/> is the last line in
+                the document.
+
+        3.  Return *exclusively* a single fenced JSON block (no prose,
+            no preamble, no summary) of the following shape:
+
+            ```json
+            [
+                {
+                    "type":           <type/>,
+                    "file":           <file/>,
+                    "line":           <line/>,
+                    "description":    <description/>,
+                    "context_before": <context-before/>,
+                    "old_text":       <old-text/>,
+                    "new_text":       <new-text/>,
+                    "context_after":  <context-after/>
+                },
+                [...]
+            ]
+            ```
+
+        4.  You *MUST* *NOT* propose, apply, or render any document
+            changes itself.
+
+    Parse the JSON array from the sub-agent's return value and set
+    <problems/> to that list.
+
+    You *MUST* *NOT* output anything at all in this step 1 beyond the
+    single `Agent` tool invocation.
+    </step>
+
+2.  <step id="STEP 2: Summary">
+
+    Use the following <template/> to give a summary of the detected
+    problems in <problems/>:
+
+    <template>
+    &#x26AA; **PROOFREADING SUMMARY**:
+
+    | *Proofread Type* | *Proofread Result*      |
+    | ---------------- | ----------------------- |
+    | **SPELLING**:    | **<n/>** problems found |
+    | **PUNCTUATION**: | **<m/>** problems found |
+    | **GRAMMAR**:     | **<k/>** problems found |
+
+    </template>
+
+    Hints:
+
+    -   <n/> is the number of problems with `type` equal to `SPELLING`    in <problems/>
+    -   <m/> is the number of problems with `type` equal to `PUNCTUATION` in <problems/>
+    -   <k/> is the number of problems with `type` equal to `GRAMMAR`     in <problems/>
+
+    </step>
+
+3.  <step id="STEP 3: Correction">
+
+    1.  You *MUST* activate the auto-approve gate for the `Edit` tool
+        by setting the session-scoped `agent.skill` configuration value
+        to this skill's name via the MCP tool call `config_set(key:
+        "agent.skill", val: "ase-docs-proofread", scope:
+        "session:<ase-session-id/>")` of the `ase` service.
+
+    2.  Iterate over all problems:
+
+        <for items="<problems/>">
+
+        1.  Set <type/>           to the `type` field of <item/>.
+            Set <file/>           to the `file` field of <item/>.
+            Set <line/>           to the `line` field of <item/>.
+            Set <description/>    to the `description` field of <item/>.
+            Set <context-before/> to the `context_before` field of <item/>.
+            Set <old-text/>       to the `old_text` field of <item/>.
+            Set <new-text/>       to the `new_text` field of <item/>.
+            Set <context-after/>  to the `context_after` field of <item/>.
+
+        2.  Report the problem with the following <template/>:
+
+            <template>
+            &#x1F7E0; **<type/> PROBLEM**: `<file/>`:<line/>:
+
+            <description/>
+            </template>
+
+        3.  <if condition="<getopt-option-auto/> is not 'true'">
+
+            Render the proposed correction as a *unified diff* with *one*
+            line of context in a fenced block based on the following <template/>:
+
+            <template>
+
+            &#x1F535; **<type/> CORRECTION**:
+
+            ```diff
+            --- <file/> (original)
+            +++ <file/> (corrected)
+            @@ -<line/>,<n/> +<line/>,<m/> @@
+             <context-before/>
+            -<old-text/>
+            +<new-text/>
+             <context-after/>
+            ```
+
+            </template>
+
+            Hints:
+            -   The <n/> is the number of lines in <old-text/>.
+            -   The <m/> is the number of lines in <new-text/>.
+
+            </if>
+
+        4.  <if condition="<getopt-option-auto/> is not 'true'">
+
+            Ask the user how to proceed via an interactive user dialog:
+
+            <expand name="user-dialog">
+                CORRECTION: How would you like to proceed with this proposed correction?
+                ACCEPT: Apply the proposed correction.
+                REFINE: Discard this proposed correction and generate a new one.
+                REJECT: Skip this proposed correction.
+            </expand>
+
+            </if>
+
+            <if condition="<getopt-option-auto/> is 'true'">
+
+            Set <result>ACCEPT</result>.
+
+            </if>
+
+        5.  Check <result/> and dispatch accordingly:
+
+            -   <if condition="<result/> is 'ACCEPT'">
+
+                Invoke the `Edit` tool to apply the change exactly as shown
+                in the diff. The operation will be auto-approved because of
+                the active proofread marker, so *no* interactive permission
+                prompt will appear. Then continue with the next <item/>.
+
+                </if>
+
+            -   <if condition="
+                    <result/> starts with 'REFINE' or
+                    <result/> starts with 'OTHER'
+                ">
+
+                Generate a *new* proposal for the *same* <item/>
+                (incorporating the user's free-text hint from <result/> if
+                provided via the "OTHER" prefix) and loop back to substep 2
+                of this iteration. There is *no* cap on refinement rounds —
+                keep refining until the user picks `ACCEPT` or `REJECT`.
+
+                </if>
+
+            -   <if condition="
+                    <result/> is 'REJECT' or
+                    <result/> is 'CANCEL' or
+                    <result/> starts with 'ERROR'
+                ">
+
+                Skip this <item/> without any `Edit` call and continue
+                with the next <item/>.
+
+                </if>
+
+        </for>
+
+    3.  After the iteration has finished, you *MUST* clear the auto-approve
+        gate via the call MCP tool call `config_delete(key:
+        "agent.skill", scope: "session:<ase-session-id/>")` of the `ase`
+        service.
+
+    4.  You *MUST* *NOT* output any further additional explanations or
+        summaries at the end of this skill processing.
+
+    </step>
+
+</flow>
+

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

@@ -33,7 +33,7 @@ based on underlying *Git* commit messages.
 </objective>
 
 For this, understand that ChangeLog entries are
-are always formatted `<prefix/>: <summary/>` where
+always formatted `<prefix/>: <summary/>` where
 the <prefix/> is one of the following tags
 and their usual related changes...
 
@@ -66,7 +66,7 @@ are also grouped and sorted according to the above <prefix/>es.
    </step>
 
 3. <step id="STEP 3: Complete ChangeLog entries">
-   Without immediately modifying `CHANGELOG.md` file,
+   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
@@ -74,17 +74,17 @@ are also grouped and sorted according to the above <prefix/>es.
    </step>
 
 4. <step id="STEP 4: Consolidate ChangeLog entries">
-   Without immediately modifying `CHANGELOG.md` file,
+   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 too less comprehensible
-   because of too less context, add some context, especially references
+   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 `CHANGELOG.md` file,
+   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.

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

@@ -3,7 +3,7 @@ name: ase-meta-chat
 argument-hint: "<llm> <query>"
 description: >
     Query foreign LLM for Chat.
-    Use this skill if a foreign LLM like OpenAI ChatCGPT, Google Gemini,
+    Use this skill if a foreign LLM like OpenAI ChatGPT, Google Gemini,
     DeepSeek or xAI Grok should be queried with a single chat message.
 user-invocable: true
 disable-model-invocation: false

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

@@ -24,7 +24,7 @@ Your role is an experienced, *expert-level software developer*,
 specialized in *Git commit messages*.
 
 <objective>
-Help to *craft* a *consise commit message* for the
+Help to *craft* a *concise commit message* for the
 currently staged Git changes.
 </objective>