new-branch-and-pr
Skill0 starsChanged 15 days agoMITView on GitHub
Create a fresh branch, complete work, and open a pull request
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- upamune/skillsword for word, first seen Nov 15, 2026
- dhanji4U/skillsedited, first seen Oct 2, 2026
- ElyzeSolutions/skillsword for word, first seen Aug 6, 2026
Other versions3 projects use a version of this.
Word for word · 2
- ElyzeSolutions/skills★ 1100% same
- upamune/skills★ 1100% same
Edited · 1
- dhanji4U/skills★ 273% same
Wrote their own version · 0
None found.
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-compiler-errorsSkill
- control-cliSkill
- control-uiSkill
- deslopSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- get-pr-commentsSkill
- loop-on-ciSkill
- make-pr-easy-to-reviewSkill
- pr-review-canvasSkill
- review-and-shipSkill
- run-smoke-testsSkill
- thermo-nuclear-code-quality-reviewSkill
- verify-thisSkill
- weekly-reviewSkill
- what-did-i-get-doneSkill
- workflow-from-chatsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ensure the working tree is clean or explicitly handled.
- Distinctive: line 15
Create a descriptive branch from the latest main.
- Distinctive: line 17
Commit focused changes and push.
- Distinctive: line 18
Create a concise PR with summary and test notes.
- Distinctive: line 22
Keep branch scope focused on one change set.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
New branch and PR
Trigger
Starting work that should be shipped through a clean branch and pull request workflow.
Workflow
- Ensure the working tree is clean or explicitly handled.
- Create a descriptive branch from the latest main.
- Complete implementation and tests.
- Commit focused changes and push.
- Create a concise PR with summary and test notes.
Guardrails
- Keep branch scope focused on one change set.
- Include verification notes before requesting review.
Output
- New branch name
- PR summary and test notes
- PR URL
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.

