What problem does it solve?
It prevents risky or messy Git commits by analyzing staged changes, blocking sensitive files, enforcing safety rules, and producing clear conventional commit messages with user confirmation.
Core Features & Use Cases
- Atomic commit planning: Groups staged changes by functionality so each commit represents one logical change.
- Conventional commit formatting: Generates messages in type(scope): description format with a mandatory attribution line.
- Sensitive file detection: Blocks commits that include common secret patterns like .env, keys, and credentials files.
- Guardrails for safe workflows: Enforces non-destructive defaults (no direct main/master commits in project mode, no skipping hooks, no amend/force-push behaviors).
- User verification gate: Presents a commit plan and requires explicit approval before creating commits.
Quick Start
Use the commit skill to plan and create safe conventional Git commits for your staged changes.