What this skill does
Triage for an open PR: classifies impact (low/med/high), review complexity, suggested owner, and the files most likely to conflict. In 2 minutes you know whether you need to look now or can leave it for later.
What you get
- A 2-sentence summary (what changes + why)
- Impact: low (style/copy), med (contained feature), high (cross-cutting / data layer)
- Review complexity: 5min, 30min, 2h, ½ day
- Suggested owner (based on git blame of the touched files)
- Risk files: missing tests, migrations, env changes
- A question to ask the author before approving
When to use
- Inbox full of PRs and you don't know where to start
- Before blocking ½ day to review each one
- To delegate a review to another dev without losing context
How it works
- You paste: PR title, description, file list, +/- lines
- The skill spots patterns: migration? env changed? new deps?
- Computes impact from the touched files + cross-references cross-cutting flags
- Estimates review time from volume + file complexity
- Generates 1-3 questions the reviewer should ask before approving
- Flags red flags (no test, no migration plan, no rollback)
Output example
PR #142 — fix(checkout): mobile overflow on PIX waiting page
Summary
overflow-hidden + min-w-0 on the checkout card so the brCode
stops spilling over on mobile. 1 file, 5 lines added, 5 removed.
Impact: low
Complexity: 5min
Owner: you (last commit on the file)
Risk files
none. Tailwind class change, no logic.
Red flags
✓ no E2E test for mobile (but the component has a snapshot)
✓ no screenshot in the PR (recommend attaching one)
Questions to ask the author
1. Did you test on iPhone 12 / 13 mini (small screens)?
2. Is the QR code still scannable at 192px (mobile size)?
Recommendation
APPROVE with a request for a mobile screenshot.Pre-reqs
None. Web search helps cross-reference earlier PRs.