branch-pr
Skill2 starsChanged 20 days agoMITView on GitHub
Branch-first PR workflow for this repo. Trigger: starting a task or opening a PR.
- Deletes or force-pushes
- Commits and pushes
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
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
- Very specific: line 16
Wait for CI green, then gh pr merge <n> --squash --delete-branch, and git checkout main && git pull.
“Common” is measured: kept by at least 6 in 10 of the 4 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
The flow
- Branch BEFORE editing.
git checkout main && git pull --ff-onlythengit checkout -b <descriptive-name>. Do this first, every task — committing tomainby mistake is the most common slip here. - Implement in work-unit commits (see
work-unit-commits). - Gate:
gofmt -l .clean,go vet ./...clean,go test -race ./...green. Regenerate and inspect any affected goldens. git push -u origin <branch>and open the PR withgh pr create(a clear What / Changes / Validation body).- Wait for CI green, then
gh pr merge <n> --squash --delete-branch, andgit checkout main && git pull.
If you committed to main by mistake
Recover without losing work:
git branch <name> (snapshot HEAD) → git reset --hard origin/main →
git checkout <name> → push.
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Gentleman-Programming/gentleman-guardian-angel★ 1.2ksame name
- 0xErwin1/dbflux★ 504same name
- svg153/skills★ 1same name
- AndyTechnologies/my-own-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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- capiko-devSkill
- chained-prSkill
- cognitive-doc-designSkill
- comment-writerSkill
- go-testingSkill
- issue-creationSkill
- work-unit-commitsSkill
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.