find-bugs

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

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/prince-appiah/green-plate-mobile --skill find-bugs-prince-appiah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/prince-appiah/green-plate-mobile/tree/main/.github/skills/find-bugs
Command: npx skills add https://github.com/prince-appiah/green-plate-mobile --skill find-bugs-prince-appiah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find bugs, security vulnerabilities, and code quality issues in changes on the current branch, enabling proactive fixes before merge.

Core Features & Use Cases

  • Phase-based security review workflow guiding input gathering, attack surface mapping, and checklist verification.
  • Structured, repeatable audit process that can be applied to feature branches, pull requests, or code audits.
  • Clear, actionable report with prioritized issues and remediation steps.

Quick Start

Run the find-bugs skill on your branch to generate a step-by-step security and quality review report.

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 feature branch before merging?

To find bugs and security vulnerabilities in a feature branch, run a static code review against the mainline diff to map the attack surface and generate a prioritized audit report with remediation steps.

What is a static analysis code review workflow for pull requests?

A static analysis code review workflow for pull requests involves gathering branch diffs, mapping the attack surface, verifying changes against a security checklist, and producing a structured audit of potential defects.

Can I audit code quality issues by comparing changes between my current branch and mainline?

Yes, you can audit code quality issues by comparing changes between your current branch and mainline, applying a structured phase-based review to identify defects and security gaps in the isolated diff.

Does branch audit static analysis work for general code reviews or only pull requests?

Branch audit static analysis works for general code reviews, feature branches, and pull requests by examining the diff between the current branch and mainline for potential security gaps and code quality issues.

What's the best way to map the attack surface of new code changes?

The best way to map the attack surface of new code changes is to follow a structured security review workflow that gathers branch inputs, identifies modified components, and verifies them against a comprehensive security checklist.