pre-pr
Skill1 starsChanged 2 days agoApache-2.0View on GitHub
Run the full local quality gate and both review subagents, then draft the pull request description. Use before pushing a branch or opening a PR.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- safe-global/safe-wallet-monorepotheir own version, first seen Nov 9, 2026
- OrionArchitekton/orion-skillstheir own version, first seen Nov 2, 2026
- TickLabVN/biopasstheir own version, first seen Nov 2, 2026
- JohnnyMcGee/claude-skillstheir own version, first seen Nov 1, 2026
- plastic-labs/honchotheir own version, first seen Oct 23, 2026
- MichinaoShimizu/kirokutheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- mongodb/mongo-go-driver★ 8.5ksame name
- plastic-labs/honcho★ 8.1ksame name
- TickLabVN/biopass★ 602same name
- safe-global/safe-wallet-monorepo★ 600same name
- asynkron/asynkron-skills★ 32same name
- MichinaoShimizu/kiroku★ 2same name
- OrionArchitekton/orion-skills★ 2same name
- Docat0209/SoloForge★ 1same name
- JohnnyMcGee/claude-skills★ 0same name
- nfeuer/project-foundation-kit★ 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 repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- fairmarkSkill
The file
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 8 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
Check git diff main...HEAD -- tests/golden: if an existing expected value changed, the PR needs the numerical-change label and maintainer …
“Common” is measured: kept by at least 6 in 10 of the 8 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
<!-- Generated from .agents/skills/pre-pr/SKILL.md by scripts/sync_agents.py. Edit the source, not this file. -->uv run just check— must be green. Fix and re-run until it is.- Classify the pull request by tier ("Effort proportional to risk" in AGENTS.md):
- Small: read the diff yourself; no review subagent.
- Substantial: run the
code-reviewersubagent once on the branch diff. Fix every finding and check each fix against the list; a second pass only for a blocking logic defect. - Numerical change: as substantial, plus
numerical-auditor. Fix discrepancies.
- The numerical audit of
mainis scheduled (weekly and at milestone end); do not run it for pull requests outside the numerical-change tier. - Check
git diff main...HEAD -- tests/golden: if an existing expected value changed, the PR needs thenumerical-changelabel and maintainer approval — say so explicitly. - Draft the PR:
- Title: Conventional Commit, citing the spec (
feat(dcf): … [SPEC-0001]). - Body: summary, requirements/AC covered, tests added, docs updated, reviewer verdicts, the PR template checklist ticked honestly.
- Title: Conventional Commit, citing the spec (
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.

