canon-pr-review

Run governed Canon PR reviews on real diffs with auditable artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a governance-bound Canon PR review workflow that ensures structured, auditable feedback on real diffs.

Core Features & Use Cases

  • Expose the Canon PR review workflow as a governed run to review real diffs.
  • Enforce preflight checks and required inputs (BASE_REF, HEAD_REF, risk/zone) before execution.
  • Produce bound artifacts under the run and attach to the correct PR review packet.

Quick Start

Start a governed Canon PR review by providing BASE_REF and HEAD_REF (or WORKTREE for uncommitted changes) and an optional OWNER.

Frequently Asked Questions about canon-pr-review

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

FAQPage Schema
How do I run a governed PR review on uncommitted changes?

Run a governed PR review on uncommitted changes by supplying the WORKTREE input instead of standard refs. This triggers Canon's preflight checks to evaluate local diffs and produce auditable review artifacts.

What is a governed Canon PR review workflow?

A governed Canon PR review workflow enforces structured preflight checks and input verification before evaluating diffs. It binds optional OWNER data and generates auditable artifacts attached directly to the run lifecycle.

Do I need BASE_REF and HEAD_REF to review a git diff?

Yes, BASE_REF and HEAD_REF are required inputs to review a git diff across branches or remotes. For uncommitted local changes, you can substitute these with the WORKTREE input to satisfy the verification checks.

Can I bind an OWNER to a Canon diff review run?

Yes, you can bind an optional OWNER to a Canon diff review run. The workflow enforces risk and zone handling while attaching the OWNER binding to the resulting auditable PR review packet.

What's the best way to automate code reviews for Canon diffs?

Automate code reviews for Canon diffs by exposing the review workflow as a governed run. This enforces preflight checks and input verification, automatically producing bound artifacts under the correct PR review packet.