panel-review

Reviews code diffs by fanning out sub-agents that each apply one installed skill as a review lens.

Updated May 18, 2024
One-click install
npx skills add https://github.com/joshhornby/dotfiles --skill panel-review-joshhornby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: panel-review
Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/panel-review
Command: npx skills add https://github.com/joshhornby/dotfiles --skill panel-review-joshhornby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-pass code reviews miss issues because one reviewer cannot hold every architectural, testing, and security standard at once. This Skill runs a composable multi-agent review where each sub-agent applies exactly one installed skill as a review lens, then adversarially verifies every finding before reporting. ## Core Features & Use Cases - Composable lens roster: Any installed skill (hexagonal-architecture, typescript-strict, testing, and more) becomes a review lens, with sensible defaults, project-trait auto-detection, and only/add/remove tokens to control the roster. - Any change boundary: Review uncommitted work-in-progress, a branch diff, a stacked layer, or a GitHub pull request — a PR is one target kind, not a precondition. - Adversarial verification: Every finding is independently checked against the actual code and classified as confirmed, refuted, or unverifiable, then synthesized into one severity-ranked report with an APPROVE / REQUEST CHANGES / NEEDS DISCUSSION recommendation. - PR-readiness gate: A built-in readiness lens classifies change paths (behavior, refactor, reduction, docs) and checks mutation-evidence freshness before a boundary ships. - Use Case: Before merging a feature branch, run /panel-review #482 thorough to fan out lenses over the PR diff, verify each finding, optionally post the ranked report back to the PR with the post token. ## Quick Start Ask the agent to run /panel-review on the current branch or a specific PR number, optionally naming the skill lenses to apply.

Frequently Asked Questions about panel-review

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

FAQPage Schema
How do I review a pull request with multiple custom review lenses?

Run /panel-review with a PR number or URL, optionally naming installed skills as lenses, for example /panel-review #482 hexagonal-architecture typescript-strict. Each lens runs as its own sub-agent and findings are verified before reporting.

How do I review uncommitted changes before creating a PR?

Use /panel-review wip to review only the working-tree and staged changes against HEAD, or run /panel-review with no arguments to review the branch diff plus uncommitted work. Reviewing before a PR exists is a first-class use.

What is the difference between panel-review and double-check?

Panel-review fans out many same-provider sub-agents, each applying one of your installed skills for broad coverage. Double-check uses one independent reviewer, ideally from a different provider, to catch shared blind spots; they compose with panel-review first and double-check last.

Can I control which review lenses run?

Yes. Name skills to add them, use only <names> to run exactly those lenses, prefix with a minus to remove one (e.g. -testing), or pass thorough to include all auto-detected conditional lenses with multi-vote verification.

Does panel-review post comments to GitHub automatically?

No. It only posts when you pass the explicit post token with a PR target, writing the report via gh pr comment or gh pr review. It never approves a PR on your behalf.

When should I not use panel-review?

During active development, use focused agents like tdd-guardian or ts-enforcer instead; panel-review is the whole-boundary review at the end. It also stops and reports when the diff is empty or the target cannot be resolved.