Menu
Use when you need the evidence bundle, lineage, and linked runtime surfaces for an existing Canon run.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | canon-inspect-evidence |
| description | Use when you need the evidence bundle, lineage, and linked runtime surfaces for an existing Canon run. |
available-nowdefault visibility: prominentInspect the evidence Canon recorded for an existing run.
RUN_IDcanon is on PATH. If missing, point to the install guide..canon/ exists. If missing, point to $canon-init.canon inspect evidence --run <RUN_ID>Approve generation... only when the target is already known and Inspect evidence remains the primary inspection affordance elsewhere.canon/ is missing, point to $canon-init.RUN_ID and does not broaden into generic conversational recovery.canon inspect evidence --run <RUN_ID>.$canon-inspect-artifacts first.$canon-approve next.$canon-status only when the user needs to re-check overall run state after inspection or resume.Approve generation... until Canon already exposed the exact target for this run.$canon-status$canon-inspect-artifacts$canon-inspect-invocationsUse when you need a governed Canon review of a real diff or pull-request range instead of a loose chat summary.
Use when a repository does not have Canon runtime state yet and you need to initialize .canon before any governed workflow.
Use when you need a governed Canon policy-shaping run to shape a new or modified policy with mandatory impact evaluation.
Use when you need a governed backlog run that decomposes bounded upstream decisions into delivery epics and slices.
Use when you need a governed Canon architecture run to record decisions, tradeoffs, and risk-gated approvals.
Use when you need a governed change run in a live codebase where invariants and existing behavior matter.