gitflow
Skill1 starsChanged 4 months agoMITView on GitHub
Source-control workflow for this project. Use this skill whenever creating branches, committing, opening or merging pull requests, promoting code between environments, tagging releases, or cleaning up branches. Also consult it before any git operation that modifies remote state, and whenever a plan includes "push", "merge", "release", or "deploy" steps.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- mithraeums/skillstheir own version, first seen Nov 1, 2026
- MiguelSavignano/claude-code-systemtheir own version, first seen Nov 1, 2026
- FradSer/skillstheir own version, first seen Oct 13, 2026
- Mindrally/skillstheir own version, first seen Oct 8, 2026
- mgiovani/cc-arsenaltheir own version, first seen Sep 25, 2026
- metalagman/agent-skillstheir own version, first seen Jan 13, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Mindrally/skills★ 275same name
- metalagman/agent-skills★ 24same name
- mgiovani/cc-arsenal★ 8same name
- MiguelSavignano/claude-code-system★ 6same name
- FradSer/skills★ 4same name
- mithraeums/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- architectureSkill
- deployment-gateSkill
- documentationSkill
- pr-gateSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Never delete dev, release, or production: Delete feature branches after merge to keep the tree clean.
- Very specific: line 26
Every PR is gated: Before merge, invoke the pr-gate skill: an advisor agent reviews the PR through the project's defined review lens and …
- Distinctive: line 32
Commit messages: imperative mood, first line ≤ 72 chars, body explains *why* when non-obvious.
- Distinctive: line 33
Keep feature branches current with dev by merging dev in.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Gitflow Skill
Branch model
feature/* ──PR──▶ dev ──PR──▶ release ──PR──▶ production| Branch | Purpose | Direct commits | Deletable |
| feature/* | All development work | YES (only here) | YES — delete after merge |
| dev | Integration | NO | NEVER |
| release | QA / release candidate | NO | NEVER |
| production | Live code | NO | NEVER |
Hard rules
- Feature branches are the only branches that accept direct commits. Everything else changes only by PR + merge commit.
- Every promotion is a PR: feature → dev, dev → release, release → production. No exceptions, no fast-forward pushes, no direct merges.
- Never delete dev, release, or production. Delete feature branches after merge to keep the tree clean.
- No force-push. No history rewrite on shared branches. No branch deletion beyond merged feature branches. If an operation would delete or rewrite anything outside a feature branch: STOP and ask the Leader.
- Every PR is gated. Before merge, invoke the
pr-gateskill: an advisor agent reviews the PR through the project's defined review lens and returns GO / NO-GO. NO-GO blocks the merge. - Promotion to production additionally requires that the release candidate has passed human QA on a real device. The Leader's approval is the final gate.
Naming and hygiene
- Branch names:
feature/<short-kebab-description>(e.g.,feature/estimate-approval-flow). - One feature per branch. Small branches merge sooner and break less.
- Commit messages: imperative mood, first line ≤ 72 chars, body explains why when non-obvious.
- Keep feature branches current with dev by merging dev in; do not rebase shared work.
Credentials
- Repository operations use scoped, least-privilege access tokens retrieved from the password manager. Never request, echo, store, or commit credentials. Never widen a token's scope to make an operation easier — ask the Leader instead.
Automated promotion protocol
When a gate passes, the agent may promote automatically via the hosting provider's API (create PR → advisor review via pr-gate → merge on GO), provided: (a) the operation is on the standard promotion path above, (b) no rule in this skill is violated, and (c) production promotions still receive explicit Leader approval before merge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.