Pantheon Multi-Reviewer (Consolidated Review)

Consolidate four code review roles into a single execution pass.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jschulte/pantheon --skill pantheon-multi-reviewer-consolidated-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pantheon Multi-Reviewer (Consolidated Review)
Source: https://github.com/jschulte/pantheon/tree/main/src/skills/pantheon-multi-reviewer
Command: npx skills add https://github.com/jschulte/pantheon --skill pantheon-multi-reviewer-consolidated-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by consolidating multiple reviewer perspectives into a single pass, reducing redundant context loading and saving significant token usage.

Core Features & Use Cases

  • Consolidated Review: Performs checks from Argus (Inspector), Nemesis (Test Quality), Cerberus (Security), and Hestia (Architecture) simultaneously.
  • Efficiency: Ideal for trivial to standard complexity stories where parallel execution is not critical, offering substantial token savings.
  • Use Case: When reviewing a small feature addition, invoke this Skill to get a comprehensive review covering task verification, test quality, security, and architectural adherence in one go, rather than initiating four separate review agents.

Quick Start

Use the Pantheon Multi-Reviewer skill to review story key '1-3' using sprint artifacts located at '/path/to/sprint/artifacts'.

Frequently Asked Questions about Pantheon Multi-Reviewer (Consolidated Review)

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

FAQPage Schema
How do I automate multi-perspective code review for standard complexity stories?

Automate multi-perspective code review by consolidating Inspector, Test Quality, Security, and Architecture checks into a single execution pass. This approach reduces redundant context loading, analyzes story requirements, and saves significant token usage during CI/CD workflows.

Can I consolidate security and architecture checks into a single code review pass?

Yes, you can consolidate security and architecture checks alongside test quality and inspection into a single pass. This unified code review optimizes token usage and review time, making it ideal for trivial to standard complexity stories.

Does this consolidated code review approach require running build and lint commands first?

Yes, consolidated code review requires the execution of build, lint, and test commands before analysis. These commands ensure the codebase is validated before the tool evaluates test coverage, security vulnerabilities, and architectural patterns.

What is the best way to save tokens when running automated code reviews on small features?

The best way to save tokens during automated code reviews is to consolidate multiple reviewer perspectives into one pass. By evaluating task verification, security, and architecture simultaneously, you avoid initiating separate review agents and reduce context loading.

When should I avoid using a consolidated code review tool?

You should avoid using a consolidated code review tool for highly complex stories where parallel execution is critical. It is designed for trivial to standard complexity stories where sequential analysis of task requirements, test coverage, and security is sufficient.

Do I need npm to run the Pantheon Multi-Reviewer?

Yes, you need npm installed as a dependency to run the Pantheon Multi-Reviewer. It utilizes npm to execute required scripts for build, lint, and test commands before performing the consolidated architectural and security analysis.