Menu
Generate the stdlib-js call signature for a BLAS/LAPACK routine
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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`).
Run test coverage analysis
Show the dependency tree for a BLAS/LAPACK routine
| name | blahpack-signature |
| description | Generate the stdlib-js call signature for a BLAS/LAPACK routine |
| argument-hint | <routine> |
Generate the stdlib-js call signature for a BLAS/LAPACK routine. Run:
python bin/signature.py $ARGUMENTS
The argument should be a path to a Fortran source file, e.g. data/BLAS-3.12.0/daxpy.f or data/lapack-3.12.0/SRC/dpotf2.f.
If the user provides just a routine name like daxpy, resolve it: check data/BLAS-3.12.0/<name>.f first, then data/lapack-3.12.0/SRC/<name>.f.