find-bugs

Analyze code diffs to identify security vulnerabilities and produce structured findings.

27|5|Updated Apr 3, 2026

Search Tags:#vulnerability #code-review #bug-detection #security-review #diff-analysis #branch-audit

Ready to run

npx skills add https://github.com/Fandry96/k3-agentic-skills --skill find-bugs-fandry96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/Fandry96/k3-agentic-skills/tree/main/skills/find-bugs
Command: npx skills add https://github.com/Fandry96/k3-agentic-skills --skill find-bugs-fandry96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when you need to review changes, perform security reviews, or audit code on the current branch.

Core Features & Use Cases

Phase-based audit workflow: Guides a disciplined, multi-phase review from input gathering to pre-conclusion audit.
Comprehensive security checklist: Enforces checks for injection, authentication, authorization, CSRF, data disclosure, and more.
Change-diff analysis: Enumerates modified files, inputs, outputs, and state changes to surface risk areas.
Audit documentation: Produces structured findings with evidence and suggested fixes for each issue.

Quick Start

Review the current branch changes, map the attack surface, and perform a full security audit using the built-in phases.

Frequently Asked Questions about find-bugs

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

FAQPage Schema

How do I find security vulnerabilities in local branch changes before merging?▼

To find security vulnerabilities in local branch changes, analyze modified file diffs and map the attack surface. A structured workflow identifies injection, authentication, and CSRF issues by enumerating inputs, outputs, and state changes to produce comprehensive findings.

What is the best way to audit code for security gaps in a pull request diff?▼

The best way to audit code for security gaps in a pull request diff is a multi-phase review. This process maps inputs and outputs, enforces a security checklist for data disclosure, verifies findings, and performs a pre-conclusion audit to document suggested fixes.

Can I use diff analysis to detect injection and authorization flaws in feature branches?▼

Yes, you can use diff analysis to detect injection and authorization flaws in feature branches. By applying a comprehensive security checklist to modified files, the analysis surfaces risk areas and verifies state changes to assess compliance.

How do I perform a code review that maps the attack surface of modified files?▼

To perform a code review that maps the attack surface of modified files, enumerate all inputs, outputs, and state changes across the diff. This structured approach enforces checks for authentication, CSRF, and data disclosure vulnerabilities.

Does branch audit workflow work for compliance checks on local code changes?▼

Yes, branch audit workflow works for compliance checks on local code changes. It guides a disciplined, multi-phase process from input gathering to a pre-conclusion audit, producing structured findings with evidence for each identified security issue.

When do I need a structured security checklist for reviewing code diffs?▼

You need a structured security checklist for reviewing code diffs when auditing feature branches for vulnerabilities. It enforces targeted checks for injection, authentication, authorization, CSRF, and data disclosure to ensure comprehensive risk assessment.