Git Workflow Skill
Guidelines for maintaining clean Git history and following best practices.
Commit Messages
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, missing semicolons, etc.
- refactor: Code change that neither fixes a bug nor adds a feature
- test: Adding or updating tests
- chore: Maintenance tasks
Guidelines
- Use imperative mood ("Add feature" not "Added feature")
- Keep subject line under 50 characters
- Wrap body at 72 characters
- Explain what and why, not how
Branching Strategy
main- Production-ready codedevelop- Integration branchfeature/*- New featuresfix/*- Bug fixesrelease/*- Release preparation
Pull Request Best Practices
- Keep PRs small and focused
- Write descriptive titles and descriptions
- Link related issues
- Request appropriate reviewers
- Respond to feedback promptly