Gitflow
Skill jzills/claude-marketplace/plugins/branching-strategy/skills/gitflow
A Claude Code plugin marketplace with skills for git workflows, code quality, safety, and more.
npx -y skills add jzills/claude-marketplace --skill gitflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the repository has been identified as using GitFlow — a remote `develop` branch exists. Provides base branches, PR targets, and merge conventions for feature, release, and hotfix branches.
SKILL.md
1.4 KB, as published. Nobody here has run it
GitFlow Branching Conventions
Branch Routing
| Branch type | Cut from | PR targets | Notes |
|---|---|---|---|
feature/*, fix/*, chore/*, refactor/*, docs/*, test/*, ci/*, perf/*, style/* | develop | develop | Day-to-day work |
release/* | develop | main (default branch) | Back-merge (main → develop) is CI/CD's responsibility post-merge |
hotfix/* | main (default branch) | main (default branch) | Critical production fixes; CI/CD back-merges to develop |
Creating a Branch
Always pull the base branch before cutting:
git checkout <base-branch> && git pull origin <base-branch>
git checkout -b <new-branch>
git push -u origin <new-branch>
Resolving the Default Branch
GitFlow repos may use main or master as the production branch. Always resolve dynamically — never hardcode:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
Use this value wherever main appears in the table above.
Detection Signal
This strategy was identified because git ls-remote --heads origin develop returned output. If that is no longer true, switch to branching-strategy:trunk.