comprehensive-code-review

Automate multi-pass code review of pull requests and post findings to GitHub.

5|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/Cygnusfear/claude-stuff --skill comprehensive-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comprehensive-code-review
Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/code-review
Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill comprehensive-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-critical, multi-pass code review to identify runtime failures, architectural concerns, and verification strategies before merge.

Core Features & Use Cases

  • 6-pass Review: Technical issues, consistency, architecture, environment, verification, and synthesis.
  • Post to GitHub: Reviews are posted as PR comments for visibility.
  • Actionable Feedback: Detailed fixes, simplifications, and questions for the developer.
  • Parallel Review Mode: Optional multiplier for consensus-based reviews.

Quick Start

Run a 6-pass ultra-critical review on a PR and POST the review to GitHub, including explicit fixes and verification commands.

Frequently Asked Questions about comprehensive-code-review

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

FAQPage Schema
How do I automate a comprehensive code review for pull requests?

Comprehensive code review automates multi-pass analysis of PRs to detect runtime failures, architectural issues, and environment compatibility risks. The Skill performs six sequential passes—technical issues, consistency, architecture, environment, verification, and synthesis—then posts detailed, actionable feedback directly to GitHub as PR comments.

What does a 6-pass code review check for?

A 6-pass review examines technical correctness, code consistency against project standards, architectural alignment, environment compatibility, verification strategies and test coverage, then synthesizes findings into actionable recommendations. Each pass applies a distinct critical lens to catch different failure categories before merge.

Can I run parallel code reviews for consensus-based feedback?

Yes, parallel review mode multiplies the review across predefined reviewer networks with explicit prompts, generating consensus-based analysis. Multiple reviewers run the same passes independently, their outputs aggregated for stronger verification and reduced blind spots in high-stakes changes.

How do I ensure code reviews post to GitHub automatically?

The Skill automatically posts review findings as GitHub PR comments with mandatory posting—no manual upload step. Reviews include explicit fixes, simplifications, and verification commands embedded in the comment for immediate developer visibility and action.

What's the difference between standard code review and ultra-critical multi-pass review?

Ultra-critical multi-pass review separates concerns across six distinct passes rather than a single holistic pass, catching architectural and environmental issues standard reviews miss. The parallel mode option adds consensus networks, stricter critical attitude, and mandatory verification command output for high-stakes or security-sensitive changes.

When should I use comprehensive code review before merging?

Use comprehensive review for ultra-critical changes, security-sensitive PRs, Phase 3 devflow stages, and high-risk architectural modifications. The 6-pass methodology identifies runtime failures, compatibility gaps, and verification gaps that single-pass review often overlooks, reducing post-merge incidents.