What problem does it solve?
Defect hunting prevents code reviews, audits, tests, and guard rules from certifying changes that only appear correct on the visible or happy path. It exposes missed data entry points, mis-calibrated thresholds, unfailable checks, incomplete findings, and unverified claims.
Core Features & Use Cases
- Entry-Point Auditing: Enumerate every writer and reader of persisted or user-visible data, including edit, cancel, failure, restore, import, sync, and migration paths.
- Executable Validation: Verify thresholds, formulas, tables, rates, and other real-world claims by executing them across their full input range against independent reference data.
- Failure-Proof Guard Rules: Ensure lint rules, CI checks, architecture tests, and shell guards can detect real violations, do not match comments, and are proven through mutation and revert testing.
- Findings Discipline: Track every issue with a stable identifier, explicit status, evidence, and recurrence-prevention rules.
- Use Case: Apply this skill during an app audit to discover an unvalidated edit path, prove a paywall threshold against reference cases, and verify that the new regression guard actually fails on a realistic defect.
Quick Start
Use the defect-hunting skill to audit the proposed change, enumerate all affected data paths, validate its constants and rules, and produce a finding register with evidence and explicit unchecked items.