pr-report
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
npx skills add majiayu000/claude-skill-registry --skill pr-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PR Report Skill Produce a maintainer-grade review of a PR, branch, or large contribution. Default posture: - understand the change before judging it - explain the system as built, not just the diff - separate architectural problems from product-scope objections - make a concrete recommendation, not a vague impression ## When to Use Use this skill when the user asks for things like: - "review this PR deeply" - "explain this contribution to me" - "make me a report or webpage for this PR" - "compare this design to similar systems" - "should I merge this?" ## Outputs Common outputs: - standalone HTML report in `tmp/reports/...` - Markdown report in `report/` or another requested folder - short maintainer summary in chat If the user asks for a webpage, build a polished standalone HTML artifact with clear sections and readable visual hierarchy. Resources bundled with this skill: - `references/style-guide.md` for visual direction and report presentation rules - `assets/html-report-starter.html` for a reusable standalone HTML/CSS starter ## Workflow ### 1. Acquire and frame the target Work from local code when possible, not just the GitHub PR page. Gather: - target branch or worktree - d
- When to Use
- Outputs
- Workflow
- 1. Acquire and frame the target
- 2. Build a mental model of the system
- 3. Review like a maintainer
- 4. Distinguish the objection type
- 5. Compare to external precedents when needed
- 6. Make the recommendation actionable
- 7. Build the artifact
- 8. Verify before handoff
- Review Heuristics
- Plugin and platform work
- Good signs
What does the pr-report skill do?
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill pr-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.