fill-coverage-gaps

This skill detects handlers with card IR but missing test scenarios, automatically generating proper test scenarios and triaging failures to keep coverage aligned with new mechanics.

The best way to automate coverage gap detection is running the coverage-gap pipeline, which refreshes the handler registry, detects uncovered handlers, generates missing scenarios, and triages failures.

The workflow refreshes the handler registry, identifies handlers that have card IR but no test scenarios, generates proper scenarios to close the gap, and triages any failures to surface issues.

Yes, the skill applies to any set-import cycle and registry refresh, producing new test scenarios and triage issues when needed to maintain coverage after new mechanics are imported.

Triaging test failures is needed because newly generated scenarios for uncovered mechanics may surface underlying issues, ensuring failures are tracked as issues before leaking into production decks.