guild-review

Review per-lane handoff receipts for spec compliance and quality.

6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/lookatitude/guild --skill guild-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guild-review
Source: https://github.com/lookatitude/guild/tree/main/skills/meta/review
Command: npx skills add https://github.com/lookatitude/guild --skill guild-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill implements a two-stage review process for per-specialist handoff receipts to ensure compliance with the spec and maintain quality. It reads compact receipts from .guild/runs/<run-id>/handoffs/ and writes a summary at .guild/runs/<run-id>/review.md, including per-lane pass/fail, blockers, and follow-ups.

Core Features & Use Cases

  • Stage 1: spec-compliance checks against the receipt fields (changed_files, opens_for, assumptions, evidence, followups) and the lane scope from the plan.
  • Stage 2: quality assessment of the evidence supporting each claim, plus notes on any risks or follow-ups.
  • Output: a compact, grep-friendly review.md that downstream steps use for verify-done and planning the next task.

Quick Start

Provide a run-wide review by invoking the skill on the current run to produce the .guild/runs/<run-id>/review.md.

Frequently Asked Questions about guild-review

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

FAQPage Schema
How do I validate spec compliance for per-lane handoff receipts?

Spec compliance for handoff receipts is validated by checking required fields like changed_files, opens_for, assumptions, evidence, and followups against the lane scope from the plan. The skill coordinates this review across receipts collected under .guild/runs/<run-id>/handoffs/.

What is a two-stage review process for handoff receipts?

A two-stage review first checks spec compliance using receipt fields and lane scope, then assesses the quality of evidence supporting each claim. It outputs a summary with per-lane pass/fail results, blockers, and follow-ups to guide downstream verification.

How do I generate a quality assessment report for handoff evidence?

You generate a quality assessment report by invoking the skill on the current run. It evaluates the evidence supporting each claim in the handoff receipts and writes a compact, grep-friendly summary to .guild/runs/<run-id>/review.md.

Do I need a specific directory structure to review handoff receipts?

Yes, you need lane receipts collected under .guild/runs/<run-id>/handoffs/, the spec available under .guild/spec, and the plan accessible under .guild/plan. The skill enforces Stage 1 and Stage 2 criteria described in guild-plan.md using these inputs.

What fields are required in a handoff receipt to pass spec compliance checks?

Handoff receipts must contain changed_files, opens_for, assumptions, evidence, and followups fields to pass spec compliance checks. The skill validates these fields against the lane scope defined in the plan during Stage 1 of the review process.

Why does my handoff receipt review fail with missing blockers or follow-ups?

Handoff receipt reviews fail when required fields like changed_files, opens_for, assumptions, evidence, or followups are missing or lack supporting evidence. The two-stage review enforces both spec compliance and quality assessment criteria before generating the review.md summary.