Coverage Check
Workflow
- Detect the project package manager and scripts:
- If
package.jsonexists, inspectscriptsfortest,coverage,test:coverage, or similar - If no
package.json, look for other common test entry points (e.g.pytest,go test,cargo test) only when clearly present
- If
- Run available checks in parallel when safe:
- Prefer an explicit coverage script when present
- Otherwise run the project's test script
- Report pass/fail and any coverage summary from the tool output
- If no test or coverage scripts exist, skip and say so clearly — do not invent a test runner
Rules
- Never invent scripts that are not defined in the project
- Prefer project-configured commands over ad-hoc one-liners
- Keep the run scoped to what the repo already supports
- On failure, surface the failing command and relevant output; do not hide errors