Menu
Run test coverage analysis
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Rigorously validate a BLAS/LAPACK routine's correctness using the property-based harness. Repeatable process — classify the routine, pick generator/scheme/property from fixed tables, sweep sizes and flags, fuzz layouts, record the level. The argument is the routine name (e.g. `dpotrf`).
Run ESLint with stdlib rules, fork rules for customization, or create new fixable rules
Review a module (or the full codebase) for convention violations, scaffolding remnants, and quality issues. The argument is the module path (e.g. `lib/blas/base/zhpmv`) or empty for full audit.
Run the full translation checklist for a BLAS/LAPACK routine. The argument is the routine name (e.g. `dpotf2`).
Show the dependency tree for a BLAS/LAPACK routine
Generate the stdlib-js module scaffold for a BLAS/LAPACK routine
| name | blahpack-coverage |
| description | Run test coverage analysis |
| argument-hint | <routine> |
Run test coverage analysis for a specific module. NEVER run coverage on the full test suite — it produces thousands of lines.
For a specific module:
node --test --experimental-test-coverage lib/<pkg>/base/<routine>/test/test.js lib/<pkg>/base/<routine>/test/test.<routine>.js lib/<pkg>/base/<routine>/test/test.ndarray.js 2>&1 | tail -30
If the user asks about the whole codebase, iterate modules individually and collect summaries — do NOT glob all test files into one command.
Parse the output and present a summary table of base.js coverage. Flag any module with line coverage below 90% as needing attention. If the user asks about a specific module, show its uncovered lines and suggest what test cases would cover them.