What problem does it solve? When reviewing a diff to gated configuration, it is hard to tell whether the change tightened or weakened a control. This Skill runs the register's checker to classify the direction of a config change between two git revisions, and honestly reports which keys it could not classify and why, instead of guessing. ## Core Features & Use Cases - Direction classification: Reports each changed config key as narrowing, loosening, or neither, with before and after values, using the register's variance.polarity declarations. - Honest declined verdicts: Reports UNCLASSIFIED with one of three specific reasons (member swap, missing polarity, executable config) rather than laundering a guess into a verdict. - Violation detection: Flags a loosening of a narrowing-only control as a violation (exit 1), and treats any mixed delta as a loosening. - One targeted fix: Offers to add a missing key to the register's variance.polarity block when that is the only fixable decline reason. - Use Case: During code review of a pull request that edits a lint or coverage config, run the skill against the merge base to see whether the change weakens any gate before approving. ## Quick Start Ask the assistant to run /register-variance against the main branch to report which way the current working tree's gated configuration moved.
