pr-deep-review

Reviews pull request diffs with surrounding code context across four technical lenses.

Updated Oct 14, 2024
One-click install
npx skills add https://github.com/tktcorporation/food-shop-search --skill pr-deep-review-tktcorporation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-deep-review
Source: https://github.com/tktcorporation/food-shop-search/tree/main/.claude/skills/pr-deep-review
Command: npx skills add https://github.com/tktcorporation/food-shop-search --skill pr-deep-review-tktcorporation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Diff-only code reviews miss broken caller contracts, duplicated bugs in similar implementations, and design inconsistencies because they never read the code surrounding the change. This Skill forces a structured deep review that reads callers, similar implementations, related tests, and downstream consumers before judging a pull request. ## Core Features & Use Cases - Four-lens evaluation: Judges specification compliance, code correctness (bugs, security, performance), code quality (naming, complexity, duplication, abstraction), and overall design consistency as separate dimensions. - Mandatory context gathering: Uses grep-based exploration to enumerate callers, find similar implementations needing the same fix, and trace how changed values are handled downstream. - Fabrication prevention and verdicts: Requires every Important-level finding to cite actually-read files and lines, and outputs a merge verdict (mergeable / needs fixes / not mergeable) with severity-rated findings. - Use Case: Before merging a multi-file refactor, ask for a deep review; the Skill greps all call sites of changed functions, checks whether sibling modules need the same fix, and reports contract mismatches with file:line evidence. ## Quick Start Ask the AI to deeply review the current branch diff against main, including surrounding code, callers, and design consistency.

Frequently Asked Questions about pr-deep-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request beyond just the diff?▼

Use grep to enumerate every caller of changed functions, search for similar implementations that may need the same fix, and check related tests. This Skill structures that process into mandatory context-gathering steps before evaluating the change across four review lenses.

What should a thorough code review checklist include?▼

A thorough checklist covers specification compliance against the issue, correctness including security and performance, code quality such as naming and duplication, and design consistency with existing architecture. Each finding should cite the actual file and line it was verified against.

How is this different from running codex review on uncommitted changes?▼

Lightweight diff-only reviews miss caller contract mismatches and duplicated bugs in sibling code. This Skill mandates actively grepping surrounding code, tracing downstream value usage, and verifying findings against actually-read files before reporting them.

When should I not use a deep PR review process?▼

Skip it for typo fixes, formatting-only changes, or one-line obvious configuration edits where surrounding context adds nothing. A lightweight diff review is sufficient for self-evident changes with no caller or design impact.

Can the review be parallelized across multiple agents?▼

Yes. For wide-ranging changes, the Skill dispatches four parallel sub-agents, one per review lens, each receiving the gathered context. Important-level findings are then verified by separate agents before being merged into the final report.