commit-msglisted

# Commit Message ## When to use Invoke this skill after `git add` and before `git commit` to draft a high-quality message. ## Steps 1. Read the staged diff (`git diff --cached`) and any linked issue. 2. Pick a type: feat, fix, docs, refactor, test, chore, perf, ci. 3. Write a subject under 72 chars: `<type>(<scope>): <imperative summary>`. 4. Add a body only when the why is non-obvious: what changed and why. 5. Reference the issue id when one exists. ## Examples - "Write a commit message for my staged changes" - "Summarize this diff as a conventional commit" ## References Use the imperative mood ("add" not "added"); never include noise like "update code" or file lists the diff already shows.