help
Skill3 starsChanged 31 days agoMITView on GitHub
pr-review help & documentation. Use for any question about the pr-review tool: how to review a PR, install, authenticate, daily usage and flags; configuration (5-level merge, YAML, env vars, models, extra paths); skill packs and review passes — how passes are selected and how to add/remove/override/list skills and packs; caching (stale data, bypass, clearing); CI/CD integration (GitHub Actions, Azure DevOps Pipelines, exit codes, --fail-on gating); companion plugins (pr-review-toolkit, code-review); performance/speed/cost/token usage and size limits; the guarantees/invariants — what pr-review always does and never does (inline-only resolvable threads, never a summary comment, never a partial file list, always detecting the stack and discovering skills/MCP/plugins) and how to audit a finished run against them with `pr-review verify`; and the internal architecture (single-session dispatch, source map, why a CLI not a pure skill).
82 other projects use a version of this.
Adopted by
Most recently taken up by
- krystaleicher/claude-skillstheir own version, first seen Nov 16, 2026
- rzaaeeff/agent-ledgertheir own version, first seen Nov 16, 2026
- tatashbar/Economic-Modeling-Studiotheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use create-stories, story-done and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 9 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 9 projects that use this
- +10 more from lilangMax
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- waynesutton/markdown-site★ 628same name
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
72 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acceptanceSkill
- validate-recipeSkill
The file
Files
pr-review — help & documentation
One skill, all the docs. Read the matching reference file for the topic — each is the full guide, kept short so this index stays cheap to load.
| If asked about… | Read |
| Quickstart: install, authenticate, daily usage, common flags | reference/pr-review-usage.md |
Publication volume vs pipeline status: --publish-min-severity, --fail-on, dry-run evidence and sticky resume | reference/pr-review-usage.md, reference/ci-integration.md |
| Configuration: 5-level merge, YAML, env vars, models, extra paths | reference/configuration.md |
| Review passes & skills: skill packs, how passes are selected, frontmatter, the on-demand index | reference/reviewers-vs-skills.md |
Managing skills & packs: add your own, packs sync/add/suggest, override, disable, list what's loaded | reference/adding-your-own-md.md |
| Companion plugins: pr-review-toolkit, code-review — install, auto-invocation, opting out | reference/companion-plugins.md |
CI/CD: GitHub Actions, Azure DevOps Pipelines, exit codes, --fail-on gating | reference/ci-integration.md |
| Caching: gather cache, invalidation, bypass flags, clearing | reference/caching.md |
| Performance: diff exclusion, pre-filtering, single-session, early-exit, size limits | reference/performance.md |
| Architecture: execution model, source map, design decisions, resume/background | reference/architecture.md |
| Guarantees: what pr-review always does and never does, and how to audit a run against them | ../../INVARIANTS.md |
Answer from the reference file's content; don't guess. When a question spans topics (e.g. "why is my large PR rejected and how do I speed it up?"), read both relevant files.
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.

