find-bugs

Run tests, inspect source files, and write a numbered bugs-summary.md.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill find-bugs-mattbobambrose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-bugs
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/code-quality/skills/find-bugs
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill find-bugs-mattbobambrose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers systematically discover, verify, and document concrete bugs and notable design issues across a project's source and tests so teams can prioritize fixes with clear evidence.

Core Features & Use Cases

  • Detects project stack from build/manifest files and locates production and test sources to analyze.
  • Runs the test suite to surface failing tests, inspects source and test files for logic errors, missing validation, resource leaks, and API surface issues.
  • Produces a structured bugs-summary.md with numbered bugs, file paths, line references, and a separate section for design observations; useful for code reviews, bug triage, and onboarding audits.

Quick Start

Run the find-bugs skill to analyze the repository, run tests, and write a detailed bugs-summary.md to the project root.

Frequently Asked Questions about find-bugs

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

FAQPage Schema
How do I find and document codebase bugs across my source and test files?

To find and document codebase bugs, run an automated analysis skill that inspects source and test files, executes test runs, and outputs a structured bugs-summary.md with numbered bugs, file paths, and line references.

What is static analysis for codebase bug finding and how does it surface failing tests?

Static analysis for codebase bug finding reviews build configurations and globs source and test files to detect logic errors and missing validation. It executes test runs to surface failing tests and outputs a consolidated bug report.

Can I use automated code review to detect logic errors and resource leaks in any software project?

You can use automated code review to detect logic errors and resource leaks in software projects that include build manifests and source/test files. The analysis adapts to your detected project stack and inspects the API surface for issues.

What's the best way to run a bug finding analysis and generate a structured bug report?

The best way to run a bug finding analysis is to execute a skill that reads your build configuration, runs the test suite, inspects code, and writes a detailed bugs-summary.md to your project root with numbered bugs and line references.

Does the bug report include design observations or only failing tests and logic errors?

The bug report includes a separate section for design observations alongside failing tests and logic errors. It produces a structured bugs-summary.md with numbered bugs, file paths, line references, and notable design issues for code reviews.

When should I not use automated bug finding for codebase analysis?

You should not use automated bug finding for codebase analysis on projects lacking build manifests or source/test files. It requires detectable build configurations to locate production and test sources for logic error inspection.