find-bugs

Audit Git branch diffs for bugs and security vulnerabilities.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill find-bugs-luminairprime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/LuminairPrime/openwrt-docs4ai-pipeline/tree/main/.agents/skills/find-bugs
Command: npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill find-bugs-luminairprime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code changes for bugs, security vulnerabilities, and quality issues is time‑consuming and error‑prone. This skill automates a thorough, structured audit of the current branch, ensuring developers catch critical problems before merging.

Core Features & Use Cases

  • Comprehensive diff analysis: Generates full diff against the default branch and iterates over every changed file.
  • Security checklist: Systematically examines inputs, database queries, auth checks, external calls, and cryptographic operations.
  • Prioritized reporting: Returns findings ordered by severity, focusing on security bugs first.

Quick Start

Ask the find‑bugs skill to review the current branch for security issues and code defects.

Frequently Asked Questions about find-bugs

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

FAQPage Schema
How do I review code changes for security vulnerabilities before merging a Git branch?

To review code changes for security vulnerabilities, you can generate a full diff against the default branch and iterate over every changed file to systematically audit inputs, database queries, auth checks, and cryptographic operations.

What is the best way to automate a bug and security audit on my current branch?

Automating a bug and security audit involves applying a predefined security checklist to systematically examine modified files, returning prioritized reporting ordered by severity with security bugs identified first.

Does this automated code review check database queries and external calls in the diff?

Yes, this automated code review systematically examines database queries, external calls, cryptographic operations, and authentication checks within the changed files of the repository diff.

How do I get prioritized reporting for security flaws found in my repository diff?

To get prioritized reporting for security flaws, you parse changed files and evaluate each modification against a security checklist, which produces findings ordered by severity with security bugs focused on first.

Can I use this to find bugs in a Git branch without a predefined security checklist?

No, finding bugs and security flaws in a Git branch requires a predefined security checklist to systematically evaluate each modification against expected security and quality standards.