ase-meta-changelog

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md <skill name="ase-meta-changelog"> Update ChangeLog Entries </skill> <expand name="getopt" arg1="ase-meta-changelog"> $ARGUMENTS </expand> <objective> Help to complete, consolidate and sort *ChangeLog* entries of the most recent *ChangeLog* section, based on underlying *Git* commits and staged changes. </objective> 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... `<change-type/> [<artifact-kind/>]: <summary/>` ...where the <change-type/> 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 <artifact-kind/> is one or more of the following *artifact* tags, classifying which kind of artifact the change primarily touches. If multiple artifact kinds apply, comma-separate them (e.g. `[arch, code]`): - `spec`: requirement/specification artifacts - `arch`: architecture...