panel-review

Orchestrate multi-seat automated pull request reviews against project rules.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill panel-review-kriscendobot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: panel-review
Source: https://github.com/kriscendobot/garden/tree/main/skills/panel-review
Command: npx skills add https://github.com/kriscendobot/garden --skill panel-review-kriscendobot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the inconsistency and lack of rigor in automated code reviews by orchestrating a multi-perspective jury panel that enforces project-wide standards and provides actionable, disposition-based feedback.

Core Features & Use Cases

  • Multi-Perspective Review: Fans out a single PR review across multiple specialized seats (e.g., security, style, performance) to ensure comprehensive coverage.
  • Cite-or-Propose Discipline: Forces every finding to either cite an existing rule or propose a new one, preventing vague or unactionable feedback.
  • Disposition-Based Workflow: Automatically categorizes findings into actionable buckets like must-fix-loop or follow-up, ensuring the maintainer's time is spent only on high-value decisions.

Quick Start

Invoke the panel review skill to initiate a full jury assessment on the current pull request.

Frequently Asked Questions about panel-review

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

FAQPage Schema
How do I automate multi-perspective pull request reviews on GitHub?

Automated pull request reviews use a multi-seat jury panel to evaluate code against project rules and design standards. This agentic workflow fans out specialized reviewers like security and style seats to ensure comprehensive PR coverage.

What is the cite-or-propose discipline in automated code review?

Cite-or-propose discipline in automated code review forces every finding to either cite an existing project rule or propose a new one. This prevents vague feedback and ensures all review findings remain traceable to documented project conventions.

How does the disposition-based workflow manage code review findings?

A disposition-based workflow manages code review findings by automatically categorizing them into actionable buckets like must-fix-loop or follow-up. This automates fixer-loop execution and ledger tracking so maintainers only handle high-value decisions.

Can I use an agentic workflow to enforce quality assurance standards in GitHub PRs?

Yes, you can use an agentic workflow to enforce quality assurance standards in GitHub PRs. The panel review process orchestrates specialized review seats that evaluate pull requests against established project rules and design standards.

What is the best way to track unresolved findings from automated PR reviews?

The best way to track unresolved findings from automated PR reviews is using a follow-up ledger. The review process manages the lifecycle of findings, automatically routing non-blocking issues to a ledger for future tracking.