review-fix-signoff-loop

Repair and re-validate workflow implementations until dual signoff agents agree.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/AgentWorkforce/ricky --skill review-fix-signoff-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-fix-signoff-loop
Source: https://github.com/AgentWorkforce/ricky/tree/main/.agents/skills/review-fix-signoff-loop
Command: npx skills add https://github.com/AgentWorkforce/ricky --skill review-fix-signoff-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of incomplete, fragile implementations that need repeated repair and re-review before separate signoff agents can confirm end-to-end correctness.

Core Features & Use Cases

  • Repairable implementation loop with fresh context: Iterates through preflight, implementation, deterministic reconcile, repair after findings, and fresh-context signoff until both independent reviewers agree.
  • Strict dual-reviewer verdict contract: Enforces a parseable verdict schema (COMPREHENSIVELY_SATISFIED | FINDINGS | BLOCKED) with required evidence fields and scope-matrix verification for multi-repo/provider/package work.
  • Deterministic gates and evidence artifacts: Uses preflight, implementation-reconcile, durable reports, and final SIGNOFF.md artifacts to maintain a truthful evidence trail suitable for PR signoff.
  • Blocked-state handling: Writes BLOCKED_NO_COMMIT.md only for true external blockers and avoids infinite loops.

Quick Start

Use this pattern to run a review-fix-signoff loop that repeatedly repairs and re-validates a workflow implementation until Claude and Codex both issue a dual pass verdict on the same final repo state.

Frequently Asked Questions about review-fix-signoff-loop

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

FAQPage Schema
How do I automate code review and repair until independent agents sign off?

Automated code review and repair loops iterate through preflight, implementation, and deterministic reconciliation, re-validating work until independent signoff agents issue a dual pass verdict. This loop uses fresh-context reviewer iterations and strict verdict contracts to ensure end-to-end completeness.

What is a strict VERDICT contract in agent workflow signoff automation?

A strict VERDICT contract in signoff automation enforces a parseable schema using COMPREHENSIVELY_SATISFIED, FINDINGS, or BLOCKED statuses. It requires specific evidence fields and scope-matrix verification to validate multi-repo and multi-provider changes before loop exit.

How do I prevent infinite loops during automated workflow repair and validation?

Prevent infinite loops during automated workflow repair by implementing blocked-state handling that writes a BLOCKED_NO_COMMIT.md artifact for true external blockers. This mechanism ensures the repairable validation loop exits cleanly when encountering genuine external dependencies.

Does CI validation work with multi-repo and multi-provider agent workflows?

CI validation works with multi-repo and multi-provider agent workflows by applying scope-matrix verification and CI/command replay mapping. Deterministic preflight and implementation-reconcile gates ensure changes are validated across all repositories and providers before signoff.

How do I maintain evidence artifacts for PR signoff in agent workflows?

Maintain evidence artifacts for PR signoff by generating durable reports and a final SIGNOFF.md file throughout the review-fix loop. These artifacts create a truthful evidence trail documenting preflight, implementation-reconcile, and fresh-context reviewer iterations.

When do I need a fresh-context reviewer iteration for code review?

Fresh-context reviewer iterations are needed when high-stakes workflow implementations require independent verification without prior context bias. Reviewers assess the final repo state repeatedly until both agents agree, ensuring fragile implementations reach end-to-end correctness.