find-bugs

To find bugs in recent code changes, you can run a comprehensive five-phase security audit that gathers diffs, maps the attack surface, applies a security checklist, verifies findings, and generates a prioritized report.

Attack surface mapping is the process of identifying inputs, outputs, authentication checks, session usage, external calls, and cryptographic operations within changed files to establish a security baseline for code review.

You can perform a security audit on modified files by applying a comprehensive checklist to each diff, covering injection, authentication, authorization, CSRF, and information disclosure vulnerabilities across multiple languages.

Yes, this bug detection workflow applies to code review, diff analysis, and audit scenarios across multiple languages and repositories without requiring specific language dependencies or external components.

The best way to generate a reproducible report is to cross-check findings with existing tests and context, assess risk, and summarize reviewed files, identified issues, and recommended fixes in a pre-conclusion audit phase.

You should not rely solely on an automated security checklist when your diff analysis requires deep contextual verification, as the workflow cross-checks findings with existing tests and surrounding context to assess remediation feasibility.