I'm ready to help you review code changes on your branch for bugs, security vulnerabilities, and code quality issues. To get started, please provide: 1. **The git diff output** — either paste the full output of `git diff master...HEAD`, or let me know the branch names if they're different 2. **Or the changed files** — if you prefer to share specific files instead Once you share the code changes, I'll follow the complete review process: - **Phase 1**: Gather all changed code - **Phase 2**: Map...
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Find Bugs?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/artubss-find-bugs)
I'm ready to help you review code changes on your branch for bugs, security vulnerabilities, and code quality issues.
To get started, please provide:
1. **The git diff output** — either paste the full output of `git diff master...HEAD`, or let me know the branch names if they're different
2. **Or the changed files** — if you prefer to share specific files instead
Once you share the code changes, I'll follow the complete review process:
- **Phase 1**: Gather all changed code
- **Phase 2**: Map the attack surface (inputs, queries, auth, external calls, crypto, etc.)
- **Phase 3**: Run through the full security checklist
- **Phase 4**: Verify each potential issue is real
- **Phase 5**: Audit my own review before reporting
I'll prioritize **security > bugs > code quality** and skip stylistic issues. For each finding, I'll explain the problem, provide evidence, and suggest a concrete fix.
Paste your changes whenever you're ready! 📋
