canon-change

Initiate governed change runs and generate change packets in live codebases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governance and bounded-change runs in live codebases ensure invariants and existing behavior are preserved during software evolution, reducing risk when introducing changes.

Core Features & Use Cases

  • Guided change intake: Initiate new change runs with explicit risk, zone, authored inputs, and optional ownership.
  • Preflight and gating: Enforce preflight checks, system-context binding, and artifact persistence to ensure safe changes.
  • Change packet generation: Produce ADR-style documentation capturing system and domain slices, invariants, and validation plans.

Quick Start

Provide risk, zone, and an initial input to start a new bounded change run and produce a change packet.

Frequently Asked Questions about canon-change

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

FAQPage Schema
How do I initiate a governed change run in a live codebase?

A preflight check validates your inputs and binds system-context before invoking Canon to produce a change packet, ensuring existing codebase behavior and invariants are preserved during the evolution process.

Do I need Canon installed to generate change packets for my repository?

Yes, Canon must be installed in the repository. The governed change run relies on Canon to execute the preflight validation and generate the final change packet capturing system and domain slices.

What is a bounded change intake in software engineering?

It is a structured initiation process requiring explicit risk, zone, and authored inputs to define boundaries before generating a governed change packet, reducing risk during software evolution.

How does a preflight check validate codebase changes before execution?

Preflight gating validates inputs and binds system-context to enforce artifact persistence, ensuring invariants and existing behavior are preserved before invoking Canon to produce a change packet.

What documentation is produced by a governed codebase change run?

The run generates ADR-style documentation within a change packet, capturing system and domain slices, invariants, and validation plans to govern the codebase modification.