consensus-loop:guide

Standardize structured evidence submissions for consensus-loop watch-file reviews.

15|4|Updated Mar 15, 2026

Search Tags:#workflow #audit #consensus #evidence #code-review #watch-file

Ready to run

npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consensus-loop:guide
Source: https://github.com/berrzebb/consensus-loop/tree/main/skills/consensus-loop
Command: npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and engineers often struggle with submitting consistent, auditable evidence during code reviews; this guide standardizes the process and reduces review cycles.

Core Features & Use Cases

Structured evidence package templates for the consensus-loop watch file.
Clear guidance on required sections (Claim, Changed Files, Test Command, Test Result, Residual Risk) and tag lifecycle.
Applicable to code submissions, reviewer feedback, and audit rejections.

Quick Start

Submit a correctly structured evidence package for the watch file using the defined evidence template.

Frequently Asked Questions about consensus-loop:guide

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

FAQPage Schema

How do I submit structured evidence for code review?▼

To submit structured evidence for code review, provide an evidence package containing required sections like Claim, Changed Files, Test Command, Test Result, and Residual Risk, ensuring your submission is auditable and passes consensus validation.

What is a consensus-loop watch file and how does it validate evidence?▼

A consensus-loop watch file is an audit mechanism that validates submitted code review evidence by enforcing required sections, formatting rules, and a tag lifecycle to ensure all submissions are consistent and auditable.

How do I format an audit evidence package for reviewer feedback?▼

Format your audit evidence package by including the defined sections: Claim, Changed Files, Test Command, Test Result, and Residual Risk, applying the correct tag lifecycle to validate your submission within the consensus-loop workflow.

What sections are required to validate watch-file evidence during a code audit?▼

Validating watch-file evidence requires sections for Claim, Changed Files, Test Command, Test Result, and Residual Risk, alongside adherence to formatting rules and the defined tag lifecycle to prevent audit rejections.

How do I handle audit rejections in a consensus review workflow?▼

Handle audit rejections by restructuring your submission according to the consensus-loop evidence template, ensuring all required sections are present and the tag lifecycle is correctly applied for successful revalidation.

Does the consensus review guide work for standard code submissions and audit rejections?▼

Yes, the consensus review guide works for standard code submissions, reviewer feedback, and audit rejections by providing structured evidence package templates that standardize the validation process across all scenarios.