Create a git commit after completing a task. Use this skill after finishing a logical unit of work to commit changes with a detailed conventional commit message. Always confirms with user before applying the commit. Never pushes to remote.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Create conventional commits after task completion with user confirmation.
git status
git diff --stat
Identify:
Use conventional commits format:
<type>(<scope>): <short description>
<body with details>
<footer>
Types:
feat: New featurefix: Bug fixdocs: Documentation onlyrefactor: Code change that neither fixes a bug nor adds a featurestyle: Formatting, missing semicolons, etc.test: Adding or updating testschore: Maintenance tasks, dependenciesExample:
feat(auth): add password reset flow
- Add forgot password endpoint
- Implement email verification token
- Add password reset form component
Closes #123
Before committing, ALWAYS:
git diff --staged # or git diff if not staged
Show the proposed commit message
Ask: "Ready to commit these changes? (yes/no)"
Wait for explicit user approval
git add -A # or specific files
git commit -m "<message>"
git log -1 --stat
git push## Proposed Commit
**Type:** feat
**Scope:** auth
**Files:**
- src/auth/reset.ts (new)
- src/components/ResetForm.tsx (new)
- src/api/routes.ts (modified)
**Message:**
feat(auth): add password reset flow
Closes #123
**Diff summary:**
3 files changed, 245 insertions(+)
---
Ready to commit these changes?