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.
Profile →npx skills add sickn33/agentic-awesome-skills --skill find-bugs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. Get the FULL diff: `git diff $(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')...HEAD` 2. If output is truncated, read each changed file individually until you have seen every changed line 3. 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? * [ ] **Authentication**: Auth
- When to Use
- Phase 1: Complete Input Gathering
- Phase 2: Attack Surface Mapping
- Phase 3: Security Checklist (check EVERY item for EVERY file)
- Phase 4: Verification
- Phase 5: Pre-Conclusion Audit
- Output Format
- Limitations
What does the find-bugs skill do?
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.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill find-bugs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.