Create a git commit following conventional commits specification.
Commit Types
- •
feat: New feature - •
fix: Bug fix - •
refactor: Code refactoring - •
test: Adding tests - •
docs: Documentation - •
style: Formatting (no code change) - •
perf: Performance improvement - •
chore: Maintenance tasks
Process
- •Run
git statusto see changes - •Run
git diff --stagedto review staged changes - •If no staged changes, suggest files to stage
- •Generate commit message based on changes:
- •Use conventional commit format:
type(scope): description - •Keep subject line under 72 characters
- •Use imperative mood ("add" not "added")
- •Include body for complex changes
- •Use conventional commit format:
Commit Message Format
code
type(scope): short description [optional body with more details] [optional footer with breaking changes or issue references]
Examples
bash
# Feature git commit -m "feat(auth): add OAuth2 login with Google provider" # Bug fix git commit -m "fix(api): handle null response from external service" # Refactor git commit -m "refactor(hooks): extract useAuth logic into separate hook"
If argument provided: $ARGUMENTS