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 branc…