From Git Workflow
Use when the user asks to choose, define, review, or document a Git branching model for a software project, including main/dev/feature/release/hotfix rules, single-developer vs team workflows, trunk-based development, protected branches, or branch naming policies. Do not use for committing code, opening PRs, tagging releases, or hotfix execution.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-workflow:git-branch-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Choose, explain, and document a Git branching strategy for a generic software project.
Choose, explain, and document a Git branching strategy for a generic software project.
.git-workflow.yml if present.${CLAUDE_PLUGIN_ROOT}/shared; if running outside Claude Code, use the nearest ancestor containing git-workflow-skills.yml.git status --short --branch, git branch -vv, and git remote -v.simple-dev-main, release-branch, and trunk-based..git-workflow.yml snippet.shared/templates/branch-policy.md.Creating branches, modifying .git-workflow.yml, or changing branch protection requires explicit user confirmation.
See shared/references/template-override.md for the standard override mechanism.
shared/references/branch-models.mdshared/references/safety-rules.mdshared/references/template-override.mdshared/templates/branch-policy.md (use resolve_template("branch-policy.md") to respect overrides)shared/scripts/check_branch_name.pygit-feature-workflow.git-commit-discipline.git-release-workflow.Return the recommended model, branch rules, protection suggestions, config snippet, and next step.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub causebefore/git-workflow-skills --plugin git-workflow