domains / families / security / find-bugs

find-bugs

combined

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

When to use

• You need a review focused on bugs, security issues, or risky code changes.
• The task involves auditing the current branch diff rather than implementing new behavior.
• You want a structured review process with checklist-driven verification against changed files.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies share the same five-phase structure, attack-surface mapping, security checklist, verification, pre-conclusion audit, and output format. However, they disagree on how to obtain the diff and on the final reporting/fixing boundary. The benchflow copy hardcodes `git diff master...HEAD`, the getsentry copy uses `gh repo view` to resolve the default branch, and the sickn33 copy requires validated commit SHAs and explicitly distinguishes review-only from combined review-and-fix requests. The sickn33 copy also adds a 'When to Use' section, an example, limitations, and stricter evidence/audit wording. Because each copy contains material steps or constraints the others lack, and they conflict on the diff command and fix authorization, crowning one would hide real alternatives.