review

Guide structured beta reviews through phases with evidence-backed verdicts.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill review-usurobor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/review
Command: npx skills add https://github.com/usurobor/cnos --skill review-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a multi-phase, evidence-backed review process that ensures contracts, diffs, and architectures are coherent before merging.

Core Features & Use Cases

  • Phase-driven review lifecycle: contract integrity, issue contract walk, diff-context, and architecture checks.
  • Evidence-based verdicts: every claim traces to artifacts with CI gate verification.
  • Governance and consistency: enforces gamma-scaffold completeness and structured rollback paths. Use cases include teams performing rigorous, auditable PR reviews and multi-phase QA for critical changes.

Quick Start

Start a beta review against the target branch to trigger Phase 1 contract integrity, Phase 2 issue contract walk, and Phase 2 diff/architecture checks.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run evidence-backed code reviews for critical pull requests?

Evidence-backed code reviews require a multi-phase process guiding reviewers through contract integrity, diff-context, and architecture checks. Every claim traces to artifacts, enforcing scaffolding completeness before producing a verifiable verdict with CI gate checks.

What is a multi-phase review process for ensuring contract integrity before merging?

A multi-phase review process orchestrates contract integrity checks, issue contract walks, and diff-context architecture checks sequentially. It ensures architectural coherence before merging by tracing every claim to artifacts and enforcing gamma-scaffold requirements before approval.

How do I trace review claims to artifacts for CI gate verification?

Trace review claims to artifacts by running a structured beta review that enforces evidence-backed verdicts through Phase 1, Phase 2a, 2b, and 2c. This produces a verifiable verdict with CI gate checks before final approval.

Can I enforce gamma-scaffold completeness during a PR review?

Yes, you can enforce gamma-scaffold completeness during a PR review by triggering a structured beta review. The process mandates gamma-scaffold requirements and structured rollback paths before granting final approval.

Does this structured review process work for multi-phase QA on critical changes?

This structured review process is designed for teams performing rigorous, auditable PR reviews and multi-phase QA for critical changes. It orchestrates contract integrity, diff-context, and architecture checks to ensure coherence before merging.

What are the limitations of automated architecture checks in code review?

Automated architecture checks in code review are limited to verifying coherence against existing contracts and diff-context. They require gamma-scaffold completeness and structured rollback paths to be established before producing a verifiable verdict.