find-bugs

To audit code changes for security flaws, this Skill applies a phase-based workflow that maps the attack surface and evaluates changed files against a formal checklist to produce a prioritized issue report with remediation suggestions.

Yes, you can use static analysis for pull requests across multiple languages. This Skill performs security reviews and compliance checks on branch changes regardless of the programming language used.

The best way to find vulnerabilities during a code review is to use a structured, phase-based workflow. This approach gathers inputs, maps attack surfaces, and applies a security checklist to surface defects with actionable evidence.

The branch audit generates a prioritized, actionable report. This report lists identified bugs and security flaws alongside evidence and specific remediation suggestions to improve software safety.

No dependencies or components are required to run this security review tool. You can initiate a branch audit directly to surface bugs and vulnerabilities in your latest local changes without external setup.

You need to perform a security assessment on local branch changes during code reviews, pull requests, or merge requests. This ensures software safety by identifying bugs and quality issues before integration.