What problem does it solve?
A markuplint rule that exists in the rules registry does not affect nu-validator bench verdicts until it is explicitly added to tests/external/bench/config.ts, leaving fixtures stuck as nu-only and hiding spec-conformance coverage.
Core Features & Use Cases
- Flat rule enablement: Adds '<rule-name>': true entries to the bench config for rules whose default behavior matches the spec-conformance lens, keeping entries alphabetical.
- Severity override: Adds '<rule-name>': { severity: 'error' } for rules whose default severity is warning but whose cited spec text is a MUST / MUST NOT, with required inline justification comments.
- Side-effect verification: Guides running yarn bench:update and yarn bench:compare, then inspecting diff snapshots to confirm nu-only fixtures flip to match-error and ml-only deltas are legitimate.
- Use Case: A contributor adds the no-contradictory-aria-prop rule to the registry, but bench fixtures remain nu-only; this Skill walks them through enabling it in the bench config and validating the verdict change.
Quick Start
Enable the no-contradictory-aria-prop rule in the nu-validator bench config and verify the affected fixtures flip from nu-only to match-error.
