bug-hunt

Find real bugs with concrete witnesses by providing your target code or stack trace for a six-lens analysis. The process generates standardized bug reports containing specific inputs, observable harm, reachability paths, and fix sketches, strictly excluding style, naming, and refactoring concerns.

Witness-based bug reporting proves a defect by producing a specific input, state, or interleaving that causes observable harm. Each report includes a concrete witness, a reachability path demonstrating how the defect manifests, and a fix sketch to enable replication and remediation.

Identify concurrency and taint bugs by applying rotating analytical lenses to individual files, commits, or entire repositories. The lens-based methodology systematically surfaces real defects across null/boundary, error-path, concurrency, taint, inconsistency, and invariant categories.

Triage code defects appearing under specific interleavings by using structured reporting formats that capture explicit witnesses, observable harm, and reachability paths. This methodology isolates real concurrency bugs from superficial issues to enable targeted remediation.

Yes, you can find invariant violations in a single file by providing the target code for analysis. The lens-based workflow scales from individual files to large repositories, applying invariant and inconsistency checks to produce verifiable defect reports.

Do not use this methodology for code review tasks involving style, naming, documentation, or refactoring. This approach strictly targets verifiable defects and observable harm, directing structural improvements to separate code scrutiny workflows.