Git Commit Helper
This skill helps create professional, well-structured git commits following best practices.
Commit Message Format
Use conventional commit format:
code
<type>(<scope>): <description> [optional body] [optional footer]
Types
- •feat: New feature
- •fix: Bug fix
- •docs: Documentation changes
- •style: Code style changes (formatting, etc.)
- •refactor: Code refactoring
- •test: Adding or modifying tests
- •chore: Maintenance tasks
Workflow
- •Run
git statusto see changes - •Run
git diffto review what changed - •Stage appropriate files (prefer specific files over
git add .) - •Create commit with descriptive message
- •Verify commit was successful
Best Practices
- •Keep commits atomic (one logical change per commit)
- •Write clear, descriptive commit messages
- •Don't commit sensitive files (.env, credentials)
- •Review changes before committing
Examples
- •"Commit my changes with a good message"
- •"Create a commit for the login feature"
- •"Stage and commit the bug fix"