On 5 sample config files it printed 13 findings (9 errors, 4 warnings) from 14 rules, each with file:line and the fix.

Who it’s for
For teams that made a Codecov or pytest/Jest coverage check a required status on pull requests and trust it to block untested merges.

What breaks, and when
With informational: true the Codecov status can never fail the build, and with || true a failing gate reports success, so PRs with no tests merge green.

What you get
• A scanner Claude runs over every codecov.yml, CI, pyproject and Jest/Vitest…

See it first
The real output of the bundled example is on getreadystack.com/skills/code-coverage-gate-check/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, then ask Claude Code: “Our coverage check on pull requests is always green, even on a PR that added no tests. Can you look at our CI and coverage config and tell me whether the gate can actually fail? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
Reads config and CI files only; it does not run tests, measure coverage or call the Codecov API.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “code-coverage-gate-check.zip”.