Agent skill · mindrally
pr-review
Focused pull request review practices with severity-ranked, file-and-line-cited findings across four angles: security, performance, tests, and architecture. Use when asked to review a pull request, review a diff or set of changes, review \"this PR,\" or provide a code review before merge.
What it needs
About 4k tokens when loaded.
What this skill does
PR Review This skill covers focused, angle-specific pull request review: picking the right lens (security, performance, tests, or architecture), producing specific and severity-ranked findings, and closing with a clear merge verdict. Workflow for Reviewing a PR 1. Pick the angle — Determine emphasis from the user's request ("security", "perf", "tests", "arch"). If unspecified, ask which angle to use, or default to security as the highest-risk default. 2. Get full file context — A diff alone routinely misses bugs that live just outside the changed lines. If only a diff is available, request the surrounding file(s) before making confident claims. 3. Review against the angle's checklist — Work through the relevant checklist below in priority order; do not mix angles unless the user asked for a full review. 4. Write specific, cited findings — Every finding names a file and line number and states the concrete defect, not a vague impression. 5. Rank by severity — Group findings as blocker, important, or nit. 6. State uncertainty explicitly — If the diff doesn't give enough context to be sure, say so and ask for more code rather than guessing. 7. End with a verdict on its own line — Safe to merge needs changes reject (or the architecture-specific verdict below). Output Discipline Applies to every review angle: Cite file path and line number for each finding. Rank findings by severity: blocker, important, nit. Be specific. "This looks risky" is not a finding; "src/auth.ts:42 — JWT secret read from request body, see line 41" is a finding. If the diff doesn't give enough context to be sure, say so explicitly and ask for the surrounding file. End with a verdict on its own line: Safe to merge needs changes reject. Angle 1: Security Review the PR for security defects, in order of priority: 1. Auth/authz — new endpoints or branches missing auth checks, role assumptions, IDOR (insecure direct object reference). 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mindrally/pr-review