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.
Best use case
rulebook-git-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using rulebook-git-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rulebook-git-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rulebook-git-workflow Compares
| Feature / Agent | rulebook-git-workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 feature - `fix`: Bug fix - `docs`: Documentation - `style`: Formatting - `refactor`: Code restructuring - `test`: Adding tests - `chore`: 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 ```markdown ## Summary Brief description of changes. ## Changes - Change 1 - Change 2 ## Testing How this was tested. ## Checklist - [ ] Tests pass - [ ] Lint passes - [ ] Documentation updated ``` ## Workflow Steps 1. Create feature branch from main 2. Make commits following conventions 3. Run quality checks before push 4. Create PR with description 5. Address review feedback 6. Squash and merge