gate-discipline-diagnoselisted

# Gate Discipline: Diagnose, Then Fix the Artefact ## Overview A failing gate is signal, not noise. The artefact is what needs fixing, not the gate. This skill walks through the correct-response hierarchy from the canonical rule [`governance/gate-discipline.md`](../../governance/gate-discipline.md) when a gate fails, named to make the reflex "diagnose, then act" rather than "silence, then proceed". The rule is the source of truth for normative content (the full enumeration of prohibited responses, tool-specific anti-pattern examples, the exception-handling protocol, the framework-alignment table). This skill is the workflow wrapper: the diagnose-then-act sequence applied to a gate failure. ## When to Use - A CI gate, lint, type check, test suite, or audit failed during the current task. - A pre-commit hook blocked a commit you are trying to make. - A required status check on a PR is showing red and you are deciding how to respond. - A generator-output `--check` reports drift between the source and the committed artefact. - You are tempted to use `--no-verify`, a blanket suppression directive, `|| true`, severity-threshold lowering, or exemption-list addition to make a gate pass. - A reviewer suggests adding the failing file to an exemption list as a drive-by fix. ## Process The correct-response hierarchy from the canonical rule, executed in order of preference: 1. **Read the failure output.** Do not act before reading the gate's actual finding. The output names the ar