ai-agents-change-controllisted

Change control for this repo. Classify a change (docs-only, investigation-only, code, plugin content, hook, workflow, ADR governance), map each class to the gates it triggers, and hold the non-negotiables with the incident behind each rule. Use when you say `classify this change`, `what gates does this change trigger`, `which rules are non-negotiable`. Do NOT use for producing test evidence (use `ai-agents-validation-and-qa`) or incident history (use `ai-agents-failure-archaeology`).
rjmurillo/ai-agents · ★ 42 · AI & Automation · score 77

Install: claude install-skill rjmurillo/ai-agents

# AI Agents Change Control  How a change moves through this repository, and the rules that never bend. This repo runs verification-based enforcement. Evidence may live in the transcript, pull request, per-issue handoff, Serena memory, or an optional session log. Jargon used once: a "gate" is an automated check that blocks progress (commit, push, or merge) until satisfied. A "drift gate" compares generated output trees against their canonical sources. A "canonical source" is the single tree you are allowed to edit; everything generated from it is read-only output. ## Triggers - `classify this change` - `what gates does this change trigger` - `which rules are non-negotiable` - `why does this gate exist` ## Process ### Phase 1: Classify the change Every change belongs to at least one class. A mixed change inherits the union of all its classes' obligations. Classify against the working tree, not against your intent: one staged file in a stricter class pulls the whole change up. | Class | You touched | Marker or obligation | |-------|-------------|----------------------| | Docs-only | Markdown prose only; no code, no generated trees | QA evidence row `SKIPPED: docs-only` (case-insensitive; ADR-034 cites it as the pre-