review-panel

Coordinate six reviewer agents to analyze code and return structured findings.

Updated Aug 27, 2026

Search Tags:#collaboration #multi-agent #code-review #parallel-analysis #review-panel #software-philosophies

Ready to run

npx skills add https://github.com/icyrainz/.dotfiles --skill review-panel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-panel
Source: https://github.com/icyrainz/.dotfiles/tree/main/claude/skills/review-panel
Command: npx skills add https://github.com/icyrainz/.dotfiles --skill review-panel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn six reviewer agents in parallel, each embodying a distinct software philosophy, to review the same codebase independently through their unique lens.

Core Features & Use Cases

Spawn six reviewer agents (Grug, Carmack, Ousterhout, Beck, Fowler, Schneier) to examine the same code from multiple perspectives.
Configure scope and focus via ARGUMENTS, enabling reviewer filtering and target file selection.
Consolidate findings into a structured report with Consensus, Tensions, and a final Verdict, including confidence, severity, and locations.

Quick Start

Provide the code context and the target files to review, then run the Review Panel to obtain parallel, multi-perspective findings.

Frequently Asked Questions about review-panel

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

FAQPage Schema

How do I run a multi-perspective code review using different software philosophies?▼

Multi-perspective code review runs by spawning six parallel reviewer agents, each embodying a distinct software philosophy like Grug, Carmack, or Beck, to independently examine the same codebase and return structured findings.

What is parallel multi-agent code analysis and how does it work?▼

Parallel multi-agent code analysis spawns six reviewer agents simultaneously to examine code from different philosophical perspectives. It parses code context from target files or diffs, applies optional reviewer filtering, and consolidates findings into a structured report.

Can I filter which reviewer agents analyze my code diffs?▼

Yes, you can configure scope and focus via ARGUMENTS, enabling specific reviewer filtering and target file selection before spawning the parallel analyses across the six available software philosophy agents.

How do I get structured code review findings with severity and confidence levels?▼

Structured code review findings are generated by consolidating parallel agent analyses into a report that includes Consensus, Tensions, and a final Verdict, complete with confidence scores, severity levels, and specific code locations.

Does multi-agent code review work without external dependencies?▼

Yes, the multi-agent code review coordination operates without external dependencies, spawning its six internal reviewer agents in parallel to analyze target files directly.

When should I use parallel code review over standard single-agent analysis?▼

Parallel code review is ideal when you need to identify tensions and consensus across multiple software philosophies, providing a broader evaluation than standard single-agent analysis through six independent philosophical perspectives.