What problem does it solve?
When the markuplint vs. nu-validator coverage benchmark surfaces a new nu-only fixture (a case where nu-validator flags markup but markuplint does not), someone must determine whether markuplint has a real coverage gap or nu is over-detecting. This Skill walks through that classification: reading the fixture, both tools' outputs, and the authoritative spec, then either extending markuplint or recording a spec-cited exclusion.
Core Features & Use Cases
- Verdict-driven triage: Drives each nu-only fixture to match-error, match-clean, or nu-over by comparing nu-validator messages against markuplint violations and the HTML/ARIA/URL Living Standards.
- Spec-cited exclusions: Records nu over-detections in excluded-ids.json with verbatim spec quotes, per-ID entries or message-substring patterns, and deferred-spec markers tied to tracking Issues.
- Determinism and fact-check gates: Pins verdicts with --concurrency 1 runs to avoid parallel flicker, and requires every file path, npm package, and spec section cited in a filed Issue to be verified first.
- Use Case: After a bench refresh surfaces a new nu-only entry for a
<source srcset> fixture, use this Skill to read the HTML LS paragraph, confirm nu is correct, extend the relevant markuplint rule, and flip the fixture to match-error.
Quick Start
Triage the newest nu-only fixture from tests/external/snapshots/diff/nu-only.json and drive its verdict to a confirmed state.