Git Flow Skill
syoslyot/git-flow-skill
Git Flow automatizado em um comando — detecção inteligente, nenhuma decisão
Ver no GitHubUma skill para Claude Code que automatiza todo o ciclo de vida do Git Flow com um único comando: /gitf. Detecta o estado atual do repositório e executa a ação apropriada (merge de feature, hotfix, release completa) sem necessidade de confirmações manuais, com suporte a branch protection, reviews automáticos e resumption de operações pausadas.
Instalação
npx convez-ai syoslyot/git-flow-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automatizar fluxo Git Flow completo sem etapas manuais
- Evitar erros ao seguir estratégia de branching em time
- Forçar disciplina de branching em agents de IA
- Release automatizado com bump de versão por semântica
Veredito

Solução pragmática que resolve um problema real: Git Flow é sólido mas tedioso. A skill entrega automação verdadeira com inteligência contextual (detecção de estado, branch protection awareness, resume de operações). Bem pensada para ambientes com ou sem GitHub.
README
A tradução para o português deste README ainda está na fila.
git-flow-skill
A Claude Code skill that turns Git Flow into a single command.
The problem
Git Flow is a solid branching strategy, but following it consistently is tedious. Even when you know the rules, you still have to remember to:
- Create the right branch from the right base
- Write a meaningful PR title
- Merge in the right order
- Bump the version in the right file
- Tag on the right commit
- Back-merge the version bump back to develop
- Clean up branches in both local and remote
In practice, one of these steps gets skipped. And when you're working with an AI agent, the agent often forgets to branch at all and starts committing directly to develop.
The solution
/gitf — one command, no decisions.
It detects where you are in the Git Flow lifecycle and executes the appropriate flow end-to-end, automatically. No confirmation prompts. No manual steps.
/gitf
That's it.
What it handles
| Your current state | What /gitf does |
|---|---|
On feature/* or fix/* | Land on develop (PR or local merge) → sync |
On hotfix/* | Land on main → tag → back-merge to develop → sync |
On develop, ahead of main | Full release: branch → bump version → land on main → tag → back-merge → clean up |
On develop, AI committed here by mistake | Detects rogue commits, creates a branch from context, moves them over, then proceeds |
On develop, in sync with main | Tells you there's nothing to release |
On main | Warns you not to work here directly |
Works with or without GitHub
/gitf detects what your environment can do and adapts — it doesn't assume GitHub:
| Environment | How branches land |
|---|---|
GitHub remote + gh logged in | Pull requests (review/CI aware, resumable) |
gh installed but not logged in | Stops and offers: log in, or switch to local mode |
A remote but no usable gh | Local --no-ff merges, then pushes the updated branch |
| No remote at all | Pure local --no-ff merges |
Detection asks a simple question — is gh installed and logged in? — not what does the remote URL look like. A logged-in gh routes to the right host on its own, so GitHub Enterprise works with no special configuration. To force a mode, set {"platform":"local"} (or "github") in .gitf/config.
Branch protection aware
If your repo has branch protection rules that require a review or waiting on CI, /gitf doesn't fail — it pauses. It saves its current progress to .gitf/state.json and tells you what's blocking.
Once the review is approved or CI passes, run /gitf again. It reads the saved state and picks up exactly where it left off.
The same pause/resume mechanism backs the pre-release code-review gate: before a release or hotfix lands on main, /gitf runs your configured review tool (chosen on first run, stored in .gitf/config). It auto-fixes what it can, and if anything needs your judgment it pauses with the findings. Fix them and run /gitf again, or bypass once with /gitf --skip-review.
Version bump logic
When releasing, /gitf reads your commit history since the last release and decides the version bump automatically:
| Commits since last release | Bump |
|---|---|
Only fix: commits | patch — 1.2.3 → 1.2.4 |
Any feat: commit | minor — 1.2.3 → 1.3.0 |
BREAKING CHANGE in body | major — 1.2.3 → 2.0.0 (asks for confirmation) |
Version file detection is automatic: package.json → pyproject.toml → Cargo.toml → VERSION. If none exist, a VERSION file is created.
Installation
Copy the gitf/ directory into your Claude Code global skills folder:
cp -r gitf/ ~/.claude/skills/gitf/
chmod +x ~/.claude/skills/gitf/gitf-update.sh
Then use /gitf in any Claude Code session across any project.
Requirements
- Claude Code
- A git repo with a
developbranch - Optional — GitHub CLI (
gh), authenticated, for the PR-based GitHub flow. Without it,/gitfruns in local-merge mode.
Automatic updates
Once installed, the skill keeps itself up to date. The first time you use /gitf each week, it silently checks this repo for a newer version. If one exists, it downloads the latest release tarball and syncs the whole gitf/ tree in the background. You'll see a one-line notice; the new version takes effect next session.
If you're upgrading from an older single-file install, the first /gitf self-heals automatically — it detects the missing flows/ and providers/ directories and pulls the full tree.
No manual update steps needed.
How merges work
All merges use merge commit (not squash or rebase). This preserves the full branch history — you can see exactly when a feature branch was created and when it landed.
Git Flow reference
This skill follows the Vincent Driessen Git Flow with a PR-based workflow:
main ────●────────────────────────────●── (production)
│ ↑
release/* merge + tag
│ │
develop ──●─●──●──●──●──●──●──●──●──────●── (integration)
↑ ↑ ↑
feature/* feature/* feature/*
| Branch | Branches from | Merges into |
|---|---|---|
feature/* | develop | develop |
fix/* | develop | develop |
release/* | develop | main AND develop |
hotfix/* | main | main AND develop |
Contributing
See CONTRIBUTING.md.
The full behavioral spec lives in spec/ — start there if you're adding a new flow or changing decision logic.