gauge

gauge

Install or tune useful static feedback for a codebase and verify that it catches representative mistakes. Use for type-checking and lint feedback loops, not claims that static checks prove correctness.

Inputs

Target language/toolchain; existing diagnostics and configuration; failures worth preventing; actual static-check command.

Run record

Use checklist 0.5 or newer for this SOP. Reading or reloading the skill must not reset work. For a new task, run checklist init "${CLAUDE_SKILL_DIR}" --new --path "/absolute/project"; retain its returned ID as RUN. For existing work, use checklist resume "$RUN", then checklist show --run "$RUN". Outside Claude, replace the skill-directory variable with this directory’s actual path.

Commands below record work after it is done. Replace evidence placeholders with concise artifact locations and observations. Manual confirmations are not independent proof; a sensor pass covers only the command and inputs it observed. verify does not close a stage; advance checks that its required readings are fulfilled. Use report --run "$RUN" for the retained history.

Before starting, inspect the project and bind TYPECHECK_CMD to its real trusted command with --var 'TYPECHECK_CMD=<actual command>'. Do not use an echo/no-op to produce a green result. checklist resume "$RUN" --var 'TYPECHECK_CMD=<new command>' changes the binding and invalidates earlier readings; commands and output are stored locally, so do not bind secrets.

Procedure

baseline

Read existing tool configuration and measure the present diagnostic baseline. Choose a feedback loop for errors that matter in this project, not a generic strictness score.

Record these artifacts after doing the work:

• Current configuration and diagnostic baseline are recorded. checklist check baseline baseline --run "$RUN" --evidence "<artifact and observation>"
• Target error classes and acceptable adoption scope are named. checklist check baseline goal --run "$RUN" --evidence "<artifact and observation>"