find-bugs

Identify and report bugs, security vulnerabilities, and quality issues in code diffs.

1|1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/sontek/agent-skills --skill find-bugs-sontek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/sontek/agent-skills/tree/main/plugins/agent-skills/skills/find-bugs
Command: npx skills add https://github.com/sontek/agent-skills --skill find-bugs-sontek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly identify bugs, security vulnerabilities, and code quality issues in branch changes, reducing review time and risk.

Core Features & Use Cases

  • Thorough, file-by-file analysis of changed code with an emphasis on security, reliability, and maintainability.
  • Structured guidance to identify common vulnerability types and quality issues across diffs.
  • Clear, actionable reporting with recommended fixes and references to best practices.
  • Use Case: When reviewing a PR that modifies authentication logic, the skill guides you to validate input handling, authorization checks, error handling, and logging for traceability.

Quick Start

Activate on the current repository state and provide the diff from main...HEAD to the skill for analysis.

Frequently Asked Questions about find-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find bugs and security vulnerabilities in a git diff?

To find bugs in a git diff, you analyze changed files across branches or pull requests to identify injection, authentication, and data handling issues. This skill systematically reviews code changes and reports vulnerabilities with evidence, impact, and actionable fixes.

What is the best way to automate code review for security issues in pull requests?

Automating code review for security involves systematically assessing changed files for authentication, data handling, and configuration concerns. This skill provides structured issue reporting with evidence, impact, and recommended fixes to reduce manual review time and risk.

Can I use this to check code quality across branch changes before merging?

Yes, you can check code quality across branch changes by applying the skill during code review of diffs from main to HEAD. It performs file-by-file analysis emphasizing security, reliability, and maintainability to ensure high-quality merges.

How do I review authentication logic changes for potential vulnerabilities?

Reviewing authentication logic changes requires validating input handling, authorization checks, error handling, and logging for traceability. The skill guides you through these specific vulnerability types and quality issues across the modified diff.

What do I need to provide to start analyzing code changes for bugs?

To start analyzing code changes for bugs, you need to activate the skill on the current repository state and provide the diff from main to HEAD. This allows the skill to assess the specific changed files for vulnerabilities and quality issues.