deep-review

Name: deep-review
Availability: InStock
Author: Ben2pc

Orchestrate multi-dimensional pull request reviews with structured reviewer assignment.

Updated Mar 12, 2026

Search Tags:#quality-assurance #code-review #pull-request #review-automation #deep-review #engineering-workflow

Ready to run

npx skills add https://github.com/Ben2pc/g-claude-code-plugins --skill deep-review-ben2pc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/Ben2pc/g-claude-code-plugins/tree/main/skills/deep-review
Command: npx skills add https://github.com/Ben2pc/g-claude-code-plugins --skill deep-review-ben2pc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-dimensional PR review orchestration that replaces ad-hoc feedback with structured, role-specific analysis and actionable punch lists.

Core Features & Use Cases

Multi-dimensional classification of changes (logic, correctness, docs-sync, UI/UX, performance, structure)
Parallel dispatch of specialized reviewers (Spec Conformance, Correctness, Documentation sync, and conditional robustness/security when needed)
Synthesize findings into a concise punch list with blocking vs non-blocking items

Quick Start

Run /deep-review on a target pull request to trigger the full review workflow.

Frequently Asked Questions about deep-review

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

FAQPage Schema

How do I automate structured pull request reviews for my engineering workflow?▼

Automated structured pull request reviews replace ad-hoc feedback by classifying changes across dimensions like logic, correctness, and performance, then dispatching specialized reviewers to synthesize a consolidated punch list of actionable items.

Why do I need a multi-dimensional code review instead of standard peer feedback?▼

Multi-dimensional code review is needed to systematically evaluate logic, correctness, documentation sync, and UI/UX, replacing unstructured peer feedback with role-specific analysis and a clear punch list of blocking versus non-blocking issues.

What's the best way to generate a consolidated punch list from PR metadata?▼

The best way to generate a consolidated punch list from PR metadata is orchestrating parallel specialized reviewers that classify changes and synthesize findings into a concise report separating blocking from non-blocking items.

Do I need the gh CLI installed to run automated PR review workflows?▼

Yes, you need the gh CLI installed because the automated PR review workflow requires it to fetch pull request metadata, classify changes across dimensions, and dispatch reviewers for the final synthesis.

Can I use automated review orchestration for pull requests of varying sizes?▼

Yes, you can use automated review orchestration for pull requests of varying sizes because the workflow applies multi-dimensional classification and structured reviewer assignment to synthesize findings regardless of PR scale.

How does deep-review classify code changes across different dimensions?▼

Deep-review classifies code changes by orchestrating parallel specialized reviewers across dimensions including spec conformance, correctness, documentation sync, and robustness to synthesize a final consolidated punch list.