Conventional Commit Assistant

When to use

Use this skill when the user asks to create a git commit or wants Conventional Commits formatting.

Workflow

1. Check repo state
   • Run git status -sb and git diff --stat.
   • If no changes, report and stop.
2. Review changes
   • Inspect relevant diffs (git diff, git diff --staged).
   • Identify the primary change intent (feature, fix, docs, etc.).
3. Confirm staging
   • If nothing is staged, ask whether to stage all (git add -A) or stage selectively.
4. Compose Conventional Commit
   • Format: type(scope): summary or type: summary.
   • Use ! for breaking changes: type(scope)!: summary.
   • Keep summary imperative, <= 50 chars if possible.
   • If needed, add body and footers (e.g., BREAKING CHANGE: ...).