find-bugs
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.
Best for Security-focused code revie…Works with GitHubLow risk
⌘source
- author
@sickn33- language
- Python
★34kstars
5.6kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Reviews branch changes for bugs and vulnerabilities
- ·Structured checklist-driven verification process
- ·Focuses on security issues like injection and XSS
- ·Analyzes attack surface of modified files
- ·Uses git diff to isolate changes
Use Cases
- →Reviewing pull requests for security vulnerabilities before merging
- →Auditing code changes for bugs and quality issues during development
- →Performing security-focused code review on current branch changes
Best for
- ✓Security-focused code reviews
- ✓Pre-merge vulnerability scanning
- ✓Development teams needing structured audit processes
Not ideal for
- !Full codebase security audits
- !Implementing new features or fixes
- !One-time static analysis of entire repositories
FAQs
name
find-bugs
description
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.
risk:unknown
source:community
Find Bugs
Review changes on this branch for bugs, security vulnerabilities, and code quality issues.
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.
Phase 1: Complete Input Gathering
- Get the FULL diff:
git diff $(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')...HEAD - If output is truncated, read each changed file individually until you have seen every changed line
- List all files modified in this branch before proceeding
Phase 2: Attack Surface Mapping
For each changed file, identify and list:
- All user inputs (request params, headers, body, URL components)
- All database queries
- All authentication/authorization checks
- All session/state operations
- All external calls
- All cryptographic operations
Phase 3: Security Checklist (check EVERY item for EVERY file)
- Injection: SQL, command, template, header injection
- XSS: All outputs in templates properly escaped?
$install
1-click copynpx skills add sickn33/antigravity-awesome-skills --skill find-bugsSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.