ase-meta-changes

name	ase-meta-changes
argument-hint
description	Update changes entries in CHANGELOG.md files
user-invocable	true
disable-model-invocation	false
effort	medium
allowed-tools	["Bash(git log *)","Bash(git status *)","Bash(git show *)","Write","Edit"]

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md

Update ChangeLog Entries

Update ChangeLog Entries

Your role is an experienced, expert-level software developer, specialized in Git version control.

Help to complete, consolidate and sort *ChangeLog* entries, based on underlying *Git* commit messages.

For this, understand that ChangeLog entries are are always formatted <prefix/>: <summary/> 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

...and

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 es.

1. 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.
2. *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.
3. Without immediately modifying `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.
4. Without immediately modifying `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
   is too short or is too less comprehensible because of too less context, add some context, especially references to the class/module/package, etc.
5. Without immediately modifying `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.
6. 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.