coverage-check

Coverage Check

Enforce the team's coverage gate: every touched file must stay ≥ 95% (line, branch, function). This skill is stack-agnostic — it runs whatever the consuming repo declares and parses whatever standard report the run produces.

1. Find the touched files

git diff --name-only against the base branch, plus staged and unstaged changes. Exclude, by convention: generated/vendored code, database migrations, and the test files themselves. Group the remaining files by the module/project they belong to so you can run the narrowest useful test set first.

2. Determine the coverage command(s)

In order of preference:

1. Declared in config — read .claude/dev-kit.json (test.coverageCommands) and the consuming repo's CLAUDE.md. If a command is declared, use it verbatim.

2. Declared by the repo's tooling — a test:coverage script in package.json, a Makefile/Taskfile target, a coverage task in the build file.

3. From the stack profile — if .claude/dev-kit.json has stacks (or you detect one), read instructions/stacks/<id>.md for the stack's coverage command, report path, and format, plus any prerequisite (e.g. PHP needs Xdebug/PCOV; without it, report that rather than 0%).

4. Detected from the stack — infer from the project files present, e.g.:

   Stack signal	Typical coverage command	Report produced
   *.csproj / *.sln	dotnet test --collect:"XPlat Code Coverage"	Cobertura XML
   package.json (jest/vitest)	npm test -- --coverage	lcov / json-summary
   angular.json	ng test --watch=false --code-coverage	lcov
   pom.xml / build.gradle	mvn test / gradle test jacocoTestReport	JaCoCo XML
   pyproject.toml / setup.py	pytest --cov --cov-report=xml	coverage.py XML
   go.mod	go test ./... -coverprofile=cover.out	Go coverprofile
   Cargo.toml	cargo llvm-cov --lcov	lcov

   A monorepo may need several commands (one per language/area). Run each and merge the per-file results.