canon-review

Coordinate governed Canon reviews of non-PR change packets with preflight validation.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apply-the/canon --skill canon-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canon-review
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-review
Command: npx skills add https://github.com/apply-the/canon --skill canon-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-PR review packets and artifact bundles require a formal, auditable governance process to ensure boundaries, evidence, and ownership before acceptance. This skill provides a structured workflow to perform such reviews within Canon.

Core Features & Use Cases

  • Structured, policy-driven review workflow for file-backed packets started from your AI assistant.
  • Enforces preflight validation (risk, zone, and exactly one authored input) and persists reviews with Canon run metadata.
  • Supports canonical review targets at canon-input/review.md or canon-input/review/ as the source material for decision making.

Quick Start

Place a single authored review packet at canon-input/review.md or canon-input/review/ with risk and zone to initiate a governed Canon review.

Frequently Asked Questions about canon-review

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

FAQPage Schema
How do I run a governed review for non-PR change packets?

Run a governed review for non-PR change packets by placing exactly one authored review file at canon-input/review.md or canon-input/review/ to initiate the Canon lifecycle and persist evidence.

What is a Canon review for non-PR packets?

A Canon review for non-PR packets is a structured, policy-driven governance workflow that enforces preflight validation, manages the review lifecycle via Canon runs, and persists auditable evidence for artifact bundles.

Does Canon review work with standard pull requests or diffs?

No, Canon review does not work with standard pull requests, diffs, or worktrees. It specifically applies to evaluating bounded non-PR change packets and artifact bundles started from your AI assistant.

What preflight validation is enforced during a non-PR packet review?

Preflight validation during a non-PR packet review enforces risk assessment, zone designation, and exactly one authored input before managing the review lifecycle via Canon runs.

How do I structure input files for an artifact bundle review?

Structure input files for an artifact bundle review by placing a single authored review packet containing risk and zone metadata at the canonical target path canon-input/review.md or canon-input/review/.

When should I use a governed review workflow instead of a standard PR review?

Use a governed review workflow instead of a standard PR review when evaluating file-backed non-PR change packets or artifact bundles that require formal preflight validation, auditable boundaries, and persisted evidence before acceptance.