find-bugs

Identify bugs and security vulnerabilities in code changes through structured static review.

Updated May 5, 2026
One-click install
npx skills add https://github.com/yanochka11/harness_bro --skill find-bugs-yanochka11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/ported/find-bugs
Command: npx skills add https://github.com/yanochka11/harness_bro --skill find-bugs-yanochka11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers identify bugs, security vulnerabilities, and quality issues in code changes through a structured static review process.

Core Features & Use Cases

  • Branch Change Review: Analyze the full diff of a code branch and inspect every modified file for potential problems.
  • Security Audit Checklist: Evaluate inputs, authentication, authorization, injection risks, data exposure, and other common vulnerability categories.
  • Verification Workflow: Validate findings against surrounding code, tests, and existing safeguards before reporting actionable issues.

Quick Start

Ask the skill to review the current branch changes for bugs and security vulnerabilities.

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 my git diff?

To find bugs and security vulnerabilities in your git diff, a structured static review inspects every modified file to map attack surfaces, verify findings, and report prioritized issues.

What is static code analysis for security audits?

Static code analysis for security audits evaluates code changes without execution to identify injection risks, data exposure, and authentication flaws by applying a security audit checklist to modified files.

How do I review branch changes for potential security issues?

Review branch changes for security issues by analyzing the full diff and applying a security audit checklist to verify inputs, authorization, and data exposure against surrounding tests before prioritizing reported issues.

Does static code review work for vulnerability detection in any codebase?

Static code review for vulnerability detection applies to software engineering workflows involving branch reviews, code audits, and security assessments, requiring complete diff analysis to map attack surfaces.

What's the best way to verify bug detection findings during a code review?

The best way to verify bug detection findings during a code review is to validate them against surrounding code, existing tests, and current safeguards before reporting prioritized actionable issues.