# Ase Meta Changelog > > - **Type:** Skill - **Install:** `agentstack add skill-rse-ase-ase-meta-changelog` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [rse](https://agentstack.voostack.com/s/rse) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** Apache-2.0 - **Upstream author:** [rse](https://github.com/rse) - **Source:** https://github.com/rse/ase/tree/master/plugin/skills/ase-meta-changelog - **Website:** https://ase.tools ## Install ```sh agentstack add skill-rse-ase-ase-meta-changelog ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md Update ChangeLog Entries $ARGUMENTS Help to complete, consolidate and sort *ChangeLog* entries of the most recent *ChangeLog* section, based on underlying *Git* commits and staged changes. Format ------ 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)`. Each *ChangeLog* entry is always formatted as `: ` where the 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 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 list. Processing ---------- 1. 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 . You *MUST* *NOT* output anything, except the result with the following : **CHANGELOG FILE:** `` 2. You *MUST* *NOT* output anything, except introduce the current operation with an output based on the following : **DETERMINE ARTIFACT CHANGES:** To update to entries of the most recent *ChangeLog* section, consult the Git *commits* plus the currently already staged changes in the Git *index*, but *ignore* the Git *stash* and still unstaged changes. For finding the corresponding Git *commits*, first determine the correct baseline Git tag. Take the `N.M.K` from the *first* (most recent) level-2 header in the *ChangeLog* file and check whether a corresponding Git tag already exists with the command `git tag --list N.M.K`. If this command produces *no* output, the first section is still in-progress/untagged, so use the `N.M.K` from the *second* level-2 header as the baseline tag instead. If this command *does* produce output, the first section is already released/tagged, so use the `N.M.K` from the *first* level-2 header as the baseline tag. Then check all Git commits between `HEAD` and this baseline 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. 3. You *MUST* *NOT* output anything, except introduce the current operation with an output based on the following : **COMPLETE 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* and *staged* changes only. For each Git commit, reduce the Git commit messages to a single short sentence, not longer than 60-80 characters. If a 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. 4. You *MUST* *NOT* output anything, except introduce the current operation with an output based on the following : **CONSOLIDATE 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 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 es. 5. You *MUST* *NOT* output anything, except introduce the current operation with an output based on the following : **UPDATING CHANGELOG:** 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. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [rse](https://github.com/rse) - **Source:** [rse/ase](https://github.com/rse/ase) - **License:** Apache-2.0 - **Homepage:** https://ase.tools Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-rse-ase-ase-meta-changelog - Seller: https://agentstack.voostack.com/s/rse - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.