review-findings-contract

Name: review-findings-contract
Availability: InStock
Author: MakerLabs

Normalize reviewer agent findings into machine-readable ledger-ready verdicts.

Updated Apr 22, 2026

Search Tags:#workflow #qa #governance #review #contract #machine-readable #findings

Ready to run

npx skills add https://github.com/mkrlabs/specflow --skill review-findings-contract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-findings-contract
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/review-findings-contract
Command: npx skills add https://github.com/mkrlabs/specflow --skill review-findings-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalized review findings for reviewers and coordinators to produce machine-readable verdicts and counts that feed the workflow ledger.

Core Features & Use Cases

Standardizes verdicts (pass/fail/needs_followup) and severity counts for reviews.
Preloads findings into reviewer agents to ensure consistent interpretation and traceability in audits.
Supports various review scopes (code, security, API contracts, accessibility, performance) within CI/governance gates.

Quick Start

Load the review findings contract into the reviewer workflow to standardize machine-readable verdicts.

Frequently Asked Questions about review-findings-contract

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

FAQPage Schema

How do I standardize code review findings into a machine-readable format for CI pipelines?▼

To standardize code review findings into a machine-readable format, you normalize outputs into a fixed REVIEW SUMMARY block containing fields like REVIEW_VERDICT and severity counts. This enables consistent integration with CI pipelines and governance controls.

What is a review findings contract and when do I need it for governance workflows?▼

A review findings contract is a standardized format that normalizes review verdicts and severity counts into a ledger-ready output. You need it for governance workflows to ensure consistent interpretation and traceability across code, security, and accessibility audits.

Can I use a single review contract format for security audits, accessibility audits, and API contract reviews?▼

Yes, you can use a single review contract format for security audits, accessibility audits, and API contract reviews. It standardizes verdicts and counts across various review scopes to ensure consistent integration within your CI governance gates.

How do I normalize reviewer agent outputs into a ledger-ready format?▼

You normalize reviewer agent outputs into a ledger-ready format by preloading the review findings contract into the workflow. This defines a fixed REVIEW SUMMARY block with verdicts and issue counts to ensure traceable, machine-readable results.

What's the best way to integrate review verdicts and severity counts into automated dashboards?▼

The best way to integrate review verdicts and severity counts into automated dashboards is to normalize findings into a fixed machine-readable REVIEW SUMMARY block. This standardizes pass, fail, and needs_followup verdicts for consistent dashboard consumption.

Does the review findings contract support needs_followup verdicts alongside pass and fail statuses?▼

Yes, the review findings contract supports needs_followup verdicts alongside pass and fail statuses. It standardizes these verdicts and top issue counts to enable consistent integration with CI pipelines and governance controls.