Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
SkillScore100Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/15/2026
What it changes
Passed 23 of 23 test cases with the skill, and 13 of 23 without it.
Without skill57%
With skill100%
Checks it passed that the model alone missed
Includes section header ## Summary
Includes Gotcha: label in commit body
Includes Decision: label in commit body
and 8 more in the full report
10 fixed13 passed either way0 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+73%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/15/2026v223 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
We need to create a branch to fix a null check crash in the billing service associated with ticket SPEC-BUG-088. Developers usually name this feature-fix or bugfix/SPEC-BUG-088-null-check. What is the exact branch name prefix format to use?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses prefix fix/ instead of bugfix/ or feature-fix/
Missed
Passed
Includes identifier SPEC-BUG-088 in the branch name
Passed
Passed
case-04 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md169 linessingle file
Git Workflow Reference
Target Agent
manager-git - Applies these patterns directly to git operations, branch management, and PR creation.
Branch Strategy Patterns
GitHub Flow (Default for Most Projects)
main ─────────────────────────────────────────
└── feat/SPEC-XXX-description ──── PR ──→ merge
Rules:
main is always deployable
Feature branches from main
PR required for all merges
Delete branch after merge
GitFlow (Complex Release Cycles)
main ──────────────────────────────────────────
└── develop ─────────────────────────────────
├── feature/SPEC-XXX ──── PR ──→ develop
└── release/v1.2.0 ────── PR ──→ main + develop
Trunk-Based (CI/CD Heavy)
main ──────────────────────────────────────────
└── short-lived branch (< 1 day) ──→ merge