panel-review-loop

Iteratively review and improve Fallow user-facing output against real-world benchmark projects.

4.4k|154|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/fallow-rs/fallow --skill panel-review-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: panel-review-loop
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/panel-review-loop
Command: npx skills add https://github.com/fallow-rs/fallow --skill panel-review-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improving a user-facing CLI surface without real-world evidence leads to regressions and guesswork. This Skill provides a disciplined loop that reviews actual Fallow output across representative real-world projects until a review panel has no blocking concerns.

Core Features & Use Cases

  • Evidence-Based Review: Captures actual output from representative projects in benchmarks/fixtures/real-world/ and runs panel-review on observed behavior rather than intended answers.
  • Iterative Improvement Loop: Implements the smallest coherent change addressing panel consensus, then re-runs the same stable corpus to compare behavior.
  • Contract Preservation: Keeps output contracts stable across iterations unless a versioned change is explicitly approved.
  • Use Case: When refining Fallow's audit report formatting, run this loop against the real-world fixture corpus to confirm each change improves the surface without breaking downstream consumers.

Quick Start

Run the panel review loop on Fallow's audit output using the real-world benchmark fixtures and iterate until the panel reports no blocking concerns.

Frequently Asked Questions about panel-review-loop

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

FAQPage Schema
How do I run the panel review loop for Fallow output?

First download the real-world fixtures with npm --prefix benchmarks run download-fixtures, then define the surface and success criteria, capture output per project, and run panel-review on the evidence. Iterate with minimal changes until the panel has no blocks.

What projects does the panel review loop test against?

It uses representative projects from benchmarks/fixtures/real-world/, an intentionally untracked corpus. You must follow the benchmark setup in BENCHMARKS.md and download the fixtures before first use.

Why is the real-world corpus untracked in the repository?

The corpus is intentionally untracked to keep the repository lean and avoid committing large third-party projects. It is fetched on demand through the benchmark fixture download script.

When should I stop iterating in the review loop?

Stop when the panel has no blocking concerns and further changes do not materially improve the surface. Keep the corpus stable across iterations so comparisons remain meaningful.

Can the loop change Fallow's output contracts?

Output contracts must be preserved across iterations unless the plan explicitly approves a versioned change. This protects downstream consumers from unexpected breaking changes.