scan-similar-bugs

Parse bug patterns and classify similar code occurrences as BUG, OK, or REVIEW.

Updated Jul 24, 2024
One-click install
npx skills add https://github.com/jasonwilmot/little-riddle --skill scan-similar-bugs-jasonwilmot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-similar-bugs
Source: https://github.com/jasonwilmot/little-riddle/tree/main/.claude/skills/scan-similar-bugs
Command: npx skills add https://github.com/jasonwilmot/little-riddle --skill scan-similar-bugs-jasonwilmot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After fixing a bug, systematically find other instances of the same pattern across the codebase to prevent regressions and ensure a broader fix.

Core Features & Use Cases

  • Pattern-based scanning: identify occurrences of a user-specified anti-pattern across the codebase and configurations.
  • Two input modes: accept a user-described bug pattern or infer from the most recent fix to prioritize scans.
  • Reporting: produce a Markdown findings file at .agents/research/YYYY-MM-DD-similar-bugs-<name>.md with per-file details and a summary.

Quick Start

Describe the bug pattern you want to find and I will locate other instances in the codebase.

Frequently Asked Questions about scan-similar-bugs

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

FAQPage Schema
How do I find similar bug patterns across my codebase after fixing a bug?

Scanning for similar bug patterns involves parsing a described anti-pattern or inferring one from recent fixes to locate matching occurrences across files and directories, classifying findings as BUG, OK, or REVIEW for regression prevention.

What is static analysis for code review and how does it prevent regressions?

Static analysis for code review prevents regressions by systematically identifying anti-pattern occurrences across a codebase after a fix, scoping relevant files, reading context, and classifying findings for broader remediation.

How do I generate a bug report for anti-pattern occurrences found during a code scan?

Scanning for anti-pattern occurrences generates a detailed Markdown report at .agents/research/YYYY-MM-DD-similar-bugs-<name>.md, containing a summary and per-file highlights of all classified BUG, OK, or REVIEW findings.

Can I scan for bug patterns without manually describing the anti-pattern?

Yes, you can scan for bug patterns without manual descriptions by using the inference mode, which automatically extracts the anti-pattern from your most recent code fixes to prioritize the scan across the codebase.

Does the bug pattern scanner require external dependencies or components?

The bug pattern scanner operates without external dependencies or components, running entirely as an autonomous static analysis agent to parse code, infer patterns, and output Markdown reports.