pr-ready
Skill11 starsChanged 29 days agoNo licenceView on GitHub
Get a PR to a decision, and leave the user able to speak to it. Outbound (our branch): hygiene, independent review through the orchestrator, a review workspace page, a teach-back, and the PR text ready to post. Inbound (their PR): the same workspace page with draft comments in the repo's conventions. Use when the user says a PR is ready, asks to "prep the PR", "run pr-ready", wants a review before submitting, or is reviewing someone else's PR ("brief me on #123", "review kit"). Offer it when substantial branch work is done and a PR is the next step.
- Commits and pushes
11 other projects use a version of this.
Adopted by
Most recently taken up by
- rhasselle-oddball/claude-skillstheir own version, first seen Nov 8, 2026
- GDriem/agent-skillstheir own version, first seen Nov 8, 2026
- rezkam/boring-but-goodtheir own version, first seen Nov 1, 2026
- thoughtspot/thoughtspot-agent-skillstheir own version, first seen Nov 1, 2026
- markoblogo/abvx-agent-skillstheir own version, first seen Nov 1, 2026
- Zwin-ux/kittheir own version, first seen Oct 11, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- remotion-dev/remotion★ 72ksame name
- rommapp/romm★ 14ksame name
- mozilla/fx-private-relay★ 1.8ksame name
- OutThisLife/brooklyn-skills★ 207same name
- block/proto-fleet★ 57same name
- markoblogo/abvx-agent-skills★ 16same name
- thoughtspot/thoughtspot-agent-skills★ 6same name
- GDriem/agent-skills★ 4same name
- rezkam/boring-but-good★ 1same name
- rhasselle-oddball/claude-skills★ 0same name
1 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 repository2 other files it gives its agents.
- deliverSkill
- orchestrationSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 11 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.
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.