pr-shepherd
Skill1 starsChanged 8 months agoNo licenceView on GitHub
Proactive PR lifecycle management through a living tracker comment pattern. Creates and maintains a single status comment on PRs that tracks review themes, implementation progress, and deferred items — from PR creation through final approval. Use when: (1) user says 'review came in', 'go over the review', 'handle the review', (2) user asks to respond to PR feedback, (3) user wants to communicate progress on a PR to reviewers, (4) user asks to create or update a PR review response, (5) you proactively detect that review comments need a structured response, (6) user says 'shepherd this PR', 'track this PR', or wants a tracker placed on a newly created PR, (7) user wants to place an initial tracker before reviews arrive, (8) you just created a PR — proactively offer to place an initial tracker.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- github/levertheir own version, first seen Nov 1, 2026
- vercel/evetheir own version, first seen Oct 20, 2026
- xdanger/skillstheir own version, first seen Oct 20, 2026
- malinskibeniamin/skillstheir own version, first seen Oct 17, 2026
- sledtools/pikatheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- vercel/eve★ 5.8ksame name
- dsifry/metaswarm★ 426same name
- github/lever★ 279same name
- sledtools/pika★ 45same name
- DogaOztuzun/branchdeck★ 18same name
- malinskibeniamin/skills★ 4same name
- ankraio/agent-tools★ 1same name
- Sassy-Dog/skills★ 1same name
- krosdai/skills★ 0same name
- xdanger/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 repository10 other files it gives its agents.
- code-reviewerSkill
- meeting-note-takerSkill
- skill-creatorSkill
- skill-quality-assessmentSkill
- speckit-constitution-primerSkill
- speckit-plan-primerSkill
- speckit-refineSkill
- speckit-roadmapSkill
- speckit-specify-primerSkill
- spec-reviewerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 20 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
20
Distinctive
This author's own choices. Worth a look.
6
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 9 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.