find-bugs

Detect bugs, security vulnerabilities, and code quality issues in local Git branch changes.

Updated Jan 24, 2026

Search Tags:#code quality #git #code review #auditing #bug detection #security vulnerabilities

Ready to run

npx skills add https://github.com/matheus3301/skills --skill find-bugs-matheus3301

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying bugs, security vulnerabilities, and code quality issues within the changes made to a local Git branch, streamlining the code review and auditing process.

Core Features & Use Cases

Comprehensive Code Review: Analyzes code changes for common and complex vulnerabilities.
Security Auditing: Checks for adherence to security best practices and potential exploits.
Bug Detection: Identifies logical errors and potential runtime issues.
Use Case: Before merging a new feature, use this Skill to perform a thorough security and bug audit on the entire branch to ensure code quality and prevent vulnerabilities.

Quick Start

Review the current branch 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 detect bugs and security vulnerabilities in my local Git branch?▼

To detect bugs and security vulnerabilities in a local Git branch, you can automate the analysis of code changes using a multi-phase approach that checks for logical errors, potential exploits, and quality issues before merging.

What is the best way to perform a security audit on code changes before merging?▼

A pre-merge security audit verifies code changes against security best practices and common exploit patterns. Running an automated check on the entire branch ensures quality assurance and prevents vulnerabilities from reaching production.

Do I need Git and GitHub CLI installed to run an automated code review?▼

Yes, Git and GitHub CLI are required dependencies for automated code review. They generate the necessary diffs and provide file access so the analysis can accurately identify bugs and quality issues in local branch changes.

How does multi-phase code analysis work for finding security flaws?▼

Multi-phase code analysis works by following a structured checklist to systematically verify changes across multiple passes. This comprehensive approach identifies both common and complex security flaws, logical bugs, and code quality issues.

Can I use automated bug detection for ongoing code quality auditing?▼

Yes, automated bug detection is applicable for ongoing code quality auditing. By analyzing local branch changes for logical errors and runtime issues, it streamlines the review process and maintains adherence to best practices.

What types of code quality issues can be found through pre-merge diff analysis?▼

Pre-merge diff analysis can identify logical errors, potential runtime issues, and security vulnerabilities. By checking adherence to best practices, it ensures comprehensive verification of code quality before changes are merged.