79573df7cb
20 specialized agents, 10 skills, 17 slash commands, 6 plugins, 12 hooks with scripts, 8 rule sets, 3 CLAUDE.md templates, 14 MCP server configs, and interactive setup installer.
1.3 KiB
1.3 KiB
Analyze the currently staged changes (git diff --cached) and generate a conventional commit message.
Steps
- Run
git diff --cached --statto see which files changed. - Run
git diff --cachedto read the actual changes. - Determine the commit type from the changes:
feat- new functionalityfix- bug fixrefactor- code restructuring without behavior changedocs- documentation onlytest- adding or updating testschore- build, CI, dependenciesperf- performance improvementstyle- formatting, whitespace
- Identify the scope from the most affected module/directory.
- Write a concise imperative subject line (max 72 chars).
- If the change is non-trivial, add a body explaining why the change was made, not what changed.
- Present the commit message for approval before executing.
Format
type(scope): subject line in imperative mood
Optional body explaining motivation and context.
Any breaking changes noted with BREAKING CHANGE: prefix.
Rules
- Subject line: imperative mood, no period, max 72 characters.
- Body: wrap at 80 characters, blank line between subject and body.
- If multiple logical changes are staged, suggest splitting into separate commits.
- Never include generated files, lock files, or build artifacts without explicit intent.