Turn repeated code concerns into falsifiable matrices that expose missing, unknown, and divergent behavior.
Ordinary review is shaped around a diff. Gap Scan inventories an entire repeated seam—routes, adapters, writers, jobs, cache mutations—and applies one explicit predicate to every instance. Absence becomes a visible row instead of something a reviewer must remember to imagine.
npx skills add TurabiOzturk/gap-scanThe CLI discovers the root skill and offers every supported agent installed on your machine. Restart the selected agent after installation.
Ask the skill to identify relevant scans for the current change:
Use $gap-scan on this change.
Or provide one bounded rule:
Use $gap-scan to inspect authorization across every route that reads customer-owned resources.
Each route must apply resource-scoped authorization before retrieval.
Gap Scan freezes the population and predicate, enumerates every instance, and records each row as
SATISFIED, VIOLATED, UNKNOWN, or NOT_APPLICABLE. Findings require direct evidence.
For reusable project rules, add .gap-scan.yaml. See the
scan-contract reference and example cases.
Gap Scan is a matrix engine, not a universal definition of good code. Its verdict is bounded by the chosen predicate and enumerated population. It does not replace architectural or contextual review.