con un clic
check-tests
Analyze test quality and coverage patterns
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Analyze test quality and coverage patterns
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | check-tests |
| description | Analyze test quality and coverage patterns |
| user_invocable | true |
| context | fork |
| agent | Explore |
Assess test quality beyond simple coverage numbers — edge cases, patterns, and completeness.
Spot-check 3 test files for coverage of error and boundary conditions:
Check that multi-case functions use table-driven patterns:
Verify decode-encode-decode cycles exist:
Spot-check 3 test files for error message assertions:
!= nil)?errors.Is() or errors.As()?err != nil without message validationCross-reference docs/testing.md critical paths with actual tests:
Find .go files without corresponding _test.go files:
## Test Quality Analysis
### Summary
| Dimension | Status | Findings |
|-----------|--------|----------|
| Edge cases | ... | ... |
| Table-driven | ... | ... |
| Round-trip tests | ... | ... |
| Error messages | ... | ... |
| Critical paths | ... | ... |
| Missing test files | ... | ... |
### Details
[Findings per dimension with file references]
### Recommendations
[Top items to improve test quality]
Audit documentation for drift, dead links, and stale content
Assess alignment with the current roadmap phase
Spot-check that code matches ADR invariants
Inventory technical debt across the codebase
Check code pattern consistency across the codebase
Run all project health checks and produce a unified report