pr-handoff
Skill363 starsChanged 13 days agoMITView on GitHub
Prepare requested pyfixest commits, pushes, and draft PRs, or an explicitly requested history cleanup. Does not authorize publication or require history rewriting.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- jonmagic/skillstheir own version, first seen Nov 8, 2026
- zajca/pohunektheir own version, first seen Oct 13, 2026
- DodoraApp/DodoStreamtheir own version, first seen Oct 8, 2026
- Vesely/skillstheir own version, first seen May 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- DodoraApp/DodoStream★ 243same name
- Vesely/skills★ 28same name
- zajca/pohunek★ 8same name
- jonmagic/skills★ 6same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- change-verificationSkill
- implementation-strategySkill
- pr-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read the applicable sections of Git and PR style: base, branch names, PR sizing, commits, PR opening, and approval.
- Distinctive: line 14
Keep coherent commits. If curation is useful, prepare the concrete rewrite described in "Approval and handoff" and use existing …
- Distinctive: line 18
After an approved rewrite, verify the final tree against the recorded tip and inspect each layer's diff.
- Very specific: line 23
Write the PR around its final outcome and material evidence, using the repository template.
“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
Hand off work
Read the applicable sections of
Git and PR style: base, branch
names, PR sizing, commits, PR opening, and approval. Reuse verification already selected
by change-verification; handoff is not a fresh test cycle.
Inspect the final diff and agent-owned history against the intended parent. Keep coherent commits. If curation is useful, prepare the concrete rewrite described in "Approval and handoff" and use existing authorization or obtain approval for that specific rewrite. A new follow-up commit is often sufficient.
After an approved rewrite, verify the final tree against the recorded tip and inspect each layer's diff. For a stack, work bottom-up and verify descendant parents before updating them; use the installed stack tool's help rather than assuming a command sequence.
Write the PR around its final outcome and material evidence, using the repository template. Carry out the requested commit/push/PR actions, submit agent-authored PRs as drafts, and stop at handoff. If only a local diff was requested, leave it local and uncommitted.
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.