ase-meta-commit

@${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-commit"> Git Commit </skill> <expand name="getopt" arg1="ase-meta-commit"> $ARGUMENTS </expand> <objective> Help to *craft* a *concise commit message* for the 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 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 (kept deliberately in sync with the intent groups of the `ase-meta-diff` and `ase-meta-changelog` skills) and their usual corresponding kind of change are: - `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 rules for generating <summary/> are: - Use a maximum of 60-80 characters - Use imperative mood ("add" not "added") - Use *no* period at the end - Use *no* M...