pr-deep-review

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

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/tktcorporation/cli-sim-game-escape --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/cli-sim-game-escape/tree/main/.claude/skills/pr-deep-review
Command: npx skills add https://github.com/tktcorporation/cli-sim-game-escape --skill pr-deep-review-tktcorporation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Diff-only code reviews miss bugs that live outside the changed lines: callers whose contracts no longer match, duplicate implementations needing the same fix, and downstream modules that consume changed values. This Skill forces a structured deep review that reads surrounding code before judging a PR. ## Core Features & Use Cases - Four-lens evaluation: Judges specification compliance, code correctness (bugs, security, performance), code quality (naming, complexity, duplication), and overall design consistency as separate dimensions. - Mandatory context gathering: Enumerates callers, similar implementations, related tests, and downstream consumers of changed symbols via grep before any verdict is issued. - Finding verification and parallel execution: Important findings must be backed by actually-read files, and large PRs can be fanned out to parallel review agents per lens. - Use Case: Before merging a multi-file refactor, ask for a deep review to confirm the changed function's new contract matches every caller and that no sibling files still carry the old buggy pattern. ## Quick Start Ask the AI to deeply review the current branch diff against main, including surrounding code, callers, and similar implementations.

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?

Gather surrounding context first: grep for callers of every changed function, find similar existing implementations, check related tests, and trace how changed values are used downstream. Then evaluate the diff against that context across specification, correctness, quality, and design lenses.

What should a thorough code review checklist include?

Cover four areas: whether the implementation matches the stated spec or issue, correctness (bugs, contract mismatches, error handling, security, performance), code quality (naming, nesting, duplication, abstraction granularity), and consistency with existing architecture and similar implementations.

How is this different from running codex review or a lightweight AI review?

Lightweight reviews inspect only the diff, so they miss caller contract mismatches and unfixed duplicate patterns elsewhere. This Skill mandates actively grepping surrounding code as a procedure, and it complements rather than replaces existing review gates.

When should I not use a deep context-heavy code review?

Skip it for typo fixes, formatting-only changes, or one-line obvious config edits where no surrounding context matters. A lightweight diff-only review is sufficient for those self-evident changes.

How do I review a large PR that touches many files?

Use the full mode: dispatch parallel agents, one per review lens (spec, correctness, quality, design), each receiving the gathered context. Verify Important-or-higher findings by re-reading the cited files before merging the results.