| name | review-static-coverage |
| description | Find gaps in static analysis where new checks could prevent classes of bugs |
| user-invocable | true |
| disable-model-invocation | true |
Enter planning mode. Deep-review production code patterns to find gaps where static analysis checks (tests/check_*.ps1) could prevent whole classes of bugs. Use maximum parallelism — spawn explore agents for independent areas.
Scope: Static analysis pre-gate checks only. NOT AHK test coverage (see review-test-coverage), NOT query tools, NOT check speed (see review-static-speed).
The Bar for a New Check
A proposed check must clear ALL of these:
- Prevents a class, not an instance — catches a pattern that can recur, not a one-off bug
- Statically detectable — regex/parsing on source files is sufficient. If it needs runtime info, skip it.
- Low false positive rate — a check that fires on 50 lines but only 2 are real problems creates noise that erodes trust in the pre-gate
- Worth the maintenance — a check that fires once a year isn't worth maintaining. Focus on patterns that are easy to introduce accidentally during normal development.
Current Check Inventory
Standalone checks (complex enough to warrant their own process):