konsistent — Fix Violations

Run konsistent, surface what is broken, and resolve violations. The hard part is not the mechanical fix — it is deciding whether the rule or the code is wrong when a single rule has many violations, and which non-trivial violations are worth attempting versus deferring.

The canonical workflow and per-predicate triage rubric are documented in node_modules/konsistent/docs/guides/fixing-violations.md. Read it before classifying violations. This skill layers strict gating, user confirmation, and AskUserQuestion interactions on top of that workflow.

Workflow (strict order)

1. Run the CLI and collect all violations as JSON.
2. Group violations by rule and identify rules with high violation counts.
3. For each high-count rule, ask the user whether to keep, change, or remove the rule.
4. Update konsistent.json via the konsistent-config skill if any rules need changes.
5. Re-run the CLI to refresh the violation list, then stop and ask for explicit confirmation before modifying any code.
6. Triage remaining violations into trivial vs. non-trivial.
7. Surface non-trivial violations to the user and let them decide how to handle each.
8. Fix the approved violations and re-run the CLI to verify.

Do not skip steps. Do not collapse them. The asks for user input at steps 3, 5, and 7 are non-negotiable.