review-output-schema

Enforce structured BLOCKING, WARNING, and Summary sections in code reviews.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill review-output-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-output-schema
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/review-output-schema
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill review-output-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes review outputs by enforcing a structured, machine-readable template that captures findings in a consistent format.

Core Features & Use Cases

  • Enforces a BLOCKING/WARNING/Summary template with an evidence section and a clear verdict.
  • Supports domain-specific findings and a composable workflow that can be reused across multiple reviews.
  • Useful for audit trails, consistent reporting, and automation-friendly review processes.

Quick Start

Provide a structured code review by applying the BLOCKING, WARNING, and Summary sections to your findings.

Frequently Asked Questions about review-output-schema

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

FAQPage Schema
How do I standardize code review outputs with a structured format?

You can standardize code review outputs by applying a machine-readable template that enforces BLOCKING, WARNING, and Summary sections with evidence. This ensures consistent reporting and audit trails across software projects.

What is a structured code review template with blocking and warning sections?

A structured code review template is a machine-readable format that separates findings into BLOCKING, WARNING, and Summary sections. It requires evidence for each finding and applies a fixed verdict rubric to standardize quality assessments.

Can I use a standardized review template for domain-specific code quality assessments?

Yes, the standardized review template supports domain-specific findings alongside its fixed BLOCKING, WARNING, and Summary sections. This allows you to tailor quality assessments to specific software project domains while maintaining a consistent output format.

How do I create an automation-friendly code review report with a clear verdict?

You can create automation-friendly review reports by enforcing a machine-readable template with a fixed verdict rubric. The structured output includes frontmatter-defined metadata and evidence-backed findings, enabling automated parsing and consistent audit trails.

What is the best way to capture evidence in a machine-readable code review output?

The best way to capture evidence in machine-readable review outputs is by using a structured template that enforces evidence sections for each BLOCKING or WARNING finding. This ensures all code review findings are backed by consistent, verifiable proof.