git-workflow
Skill6 starsChanged 7 days agoMITView on GitHub
Branch, commit and PR flow of this repo. Use whenever you create branches, commits, pushes or pull requests.
- Commits and pushes
187 other projects use a version of this.
Adopted by
Most recently taken up by
- avpit/claude-skillstheir own version, first seen Nov 16, 2026
- AlejandroGodius/claude-skillstheir own version, first seen Nov 16, 2026
- RichardMcQuiston01/unofficial-claude-skill-examplestheir own version, first seen Nov 16, 2026
- AndresArreguy/ecc-pi-porttheir own version, first seen Nov 16, 2026
- fabioc-aloha/Alex_ACT_ONEtheir own version, first seen Nov 15, 2026
- juninmd/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use squad-commands, ci-cd-pipelines and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillsquad-commands
Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.
Also in 5 projects that use this
harrissohail6Skillci-cd-pipelines
CI/CD pipeline design and implementation. Auto-activates when discussing deployment, automation, or pipelines.
Also in 6 projects that use this
Microsoft AzureSkillarchitectural-proposals
How to write comprehensive architectural proposals that drive alignment before code is written
Also in 4 projects that use this
GitHubSkille2e-template-testing
End-to-end validation of coordinator and agent template changes
Also in 3 projects that use this
GitHubSkillnotification-routing
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
Also in 3 projects that use this
frostneySkillnative-nostalgia-stack
Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.
Also in 3 projects that use this
- +5 more from Azure
- +1 more from github
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- langfuse/langfuse★ 37ksame name
- modelcontextprotocol/typescript-sdk★ 14ksame name
- JetBrains/ideavim★ 10ksame name
- jokob-sk/NetAlertX★ 7.4ksame name
- netalertx/NetAlertX★ 7.4ksame name
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- github/gh-aw★ 5.6ksame name
- modelcontextprotocol/csharp-sdk★ 4.6ksame name
- antonbabenko/pre-commit-terraform★ 3.8ksame name
- github/squad★ 3.4ksame name
177 more not listed
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- add-memberSkill
- create-issueSkill
- db-migrationSkill
- debugSkill
- implement-issueSkill
- improve-skillsSkill
- orchestrateSkill
- plan-featureSkill
- project-statusSkill
- remove-memberSkill
- review-prSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 164 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If there is no issue, ask whether to open one (skill create-issue) before inventing the number.
- Very specific: line 22
Freeze: Only fixes for that version go into release/vX.Y.Z, through a PR based on release/vX.Y.Z.
- Distinctive: line 46
Never push directly to the trunk branches.
- Very specific: line 50
If it changes a rule from an ADR, audit or plan: label business-logic and explain it in "Business logic affected".
“Common” is measured: kept by at least 6 in 10 of the 164 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
Git workflow — <PROJECT>
Details in docs/github-naming-convention.md. Mandatory summary in AGENTS.md.
Branches
- <BRANCH_RULE> Create the working branch from an up-to-date
<BASE_BRANCH>. - Name:
claude/<issue-no>-<description>(agent) or<type>/<issue-no>-<description>(person). Lowercase, numbers and hyphens only. - If there is no issue, ask whether to open one (skill
create-issue) before inventing the number.
<!-- releases:start -->Releases (develop → release/* → main)
To publish without touching production until the version is tested:
- Cut the release from an up-to-date
develop:release/vX.Y.Z(SemVer, see convention §8). From then ondevelopkeeps receiving work for the next version. - Freeze. Only fixes for that version go into
release/vX.Y.Z, through a PR based onrelease/vX.Y.Z. No new features. - Test the release in the staging environment before merging.
- Publish: PR
release/vX.Y.Z→main. On merge, tagvX.Y.Zonmain. - Return to
develop: PRmain→develop(orrelease/vX.Y.Z→develop) so the release fixes are not lost. Then therelease/*branch is deleted.
Hotfix (something broken in production):
- It comes off
main:hotfix/<issue-no>-<description>, PR tomain, PATCH tag (vX.Y.Z+1). - It always goes back to
develop, and to the openrelease/*if there is one. If it does not go back, the bug reappears in the next version.
An agent does not cut releases, merge to main or create tags unless explicitly asked.
<!-- releases:end -->Commits
<type>(<scope>): <description>— imperative, lowercase, no period, ≤ 72 characters. Types in English; the description in <COMMIT_LANG>.
<!-- template:start -->- In this repo (the template itself) the descriptions are in Spanish.
<!-- template:end -->- One commit = one logical change. If it touches several scopes: no scope, or split.
- Breaks compatibility:
feat(api)!: …+ footerBREAKING CHANGE: ….
Pull requests
- Never push directly to the trunk branches. Everything goes in through a PR.
- Title with the same format as a commit.
- Body from
.github/pull_request_template.md: What changes / Why / Business logic affected / How to test it /Closes #n. - Labels: exactly one
type:(claude/branches do not get it automatically: set it yourself), 1–2area:, nopriority:. Only labels from.github/labels.yml. - If it changes a rule from an ADR, audit or plan: label
business-logicand explain it in "Business logic affected".
gh pr create --base <BASE_BRANCH> --title "fix(api): …" --body-file <file> --label "type:bug" --label "area:api"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.

