rulebook-git-workflow
Git workflow standards including branching strategy, commit conventions, and PR guidelines. Use when creating branches, writing commit messages, preparing pull requests, or following git best practices.
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for Git workflow management, ensuring consistency across development teams. It enforces standardized branch naming conventions, Conventional Commit formats, and structured Pull Request guidelines. By integrating these best practices, teams can improve repository maintainability, facilitate easier debugging through clear history, and enhance the overall quality of the software development lifecycle (SDLC).
Use Cases
- Standardizing Branch Creation: Automatically generate branch names like 'feature/task-id-description' to maintain a clean and searchable repository structure.
- Conventional Commit Authoring: Assist developers in crafting professional commit messages that follow the type(scope): subject format, enabling automated changelog generation.
- Pull Request Preparation: Generate detailed PR descriptions with summaries, change lists, and testing checklists to improve code review efficiency and communication.
- Team Onboarding and Compliance: Serve as an interactive guide for new team members to ensure all contributions align with established organizational Git standards and best practices.
| name | rulebook-git-workflow |
|---|---|
| description | Git workflow standards including branching strategy, commit conventions, and PR guidelines. Use when creating branches, writing commit messages, preparing pull requests, or following git best practices. |
| version | "1.0.0" |
| category | core |
| author | "HiveLLM" |
| tags | ["git", "workflow", "branching", "commits", "pull-requests"] |
| dependencies | [] |
| conflicts | [] |
Git Workflow Standards
Branch Naming
feature/<task-id>-<short-description>
fix/<issue-id>-<short-description>
refactor/<scope>-<description>
docs/<scope>-<description>
Commit Message Format
<type>(<scope>): <subject>
<body>
<footer>
Types
feat: New featurefix: Bug fixdocs: Documentationstyle: Formattingrefactor: Code restructuringtest: Adding testschore: Maintenance
Example
feat(auth): add JWT token validation
Implement JWT validation middleware for protected routes.
Closes #123
Pull Request Guidelines
PR Title
feat(scope): short description
PR Description
## Summary
Brief description of changes.
## Changes
- Change 1
- Change 2
## Testing
How this was tested.
## Checklist
- [ ] Tests pass
- [ ] Lint passes
- [ ] Documentation updated
Workflow Steps
- Create feature branch from main
- Make commits following conventions
- Run quality checks before push
- Create PR with description
- Address review feedback
- Squash and merge