bugReport

You can generate a read-only bug report by running configured typecheck, lint, and test suites without altering source files. This process produces structured diagnostic findings and computes health metrics for testing, typing, and linting to capture current code health.

Codebase triage involves auditing failure-prone modules to categorize findings into bugs, tech debt, and test gaps. Health metrics score testing, typing, and linting states, helping you assess troubled modules and prioritize engineering efforts before making repairs.

Yes, you can execute typecheck, lint, and test suites even when issues exist. The diagnostic process runs in a read-only mode, ensuring no source code or tests are modified while aggregating tool outputs into categorized findings.

The best way to surface severity-ranked issues is to run a read-only code audit that aggregates defects, debts, and gaps. This generates structured reports with health metrics, providing necessary guidance for subsequent bug hunt workflows.

Yes, a read-only code audit separates false positives from actual bugs and tech debt. It aggregates tool outputs into categorized findings, ensuring your structured diagnostic reports accurately reflect the codebase's true defects and test gaps.