scan-similar-bugs

Scan codebases for recurring bug patterns and generate Markdown reports.

49|9|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Terryc21/xcode-workflow-skills --skill scan-similar-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-similar-bugs
Source: https://github.com/Terryc21/xcode-workflow-skills/tree/main/skills/scan-similar-bugs
Command: npx skills add https://github.com/Terryc21/xcode-workflow-skills --skill scan-similar-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Discover recurring anti-patterns by scanning multiple files for the target bug pattern.
  • Generate a structured findings report and save it to a date-stamped Markdown file under .agents/research.
  • Support two workflows: describe the bug pattern manually or infer it from recent fixes, then execute the scan.

Quick Start

Describe the bug pattern you're looking for or choose to infer from the most recent fix, then initiate the scan.

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 bugs in other files after fixing a code issue?

To find similar bugs, you can scan your multi-file codebase for recurring anti-patterns by either describing the bug pattern manually or inferring it from recent edits. The scan identifies matching instances and generates a structured Markdown report.

What is the best way to search a codebase for recurring anti-patterns to prevent regressions?

The best way to search for recurring anti-patterns is using automated pattern matching across multiple files after a bug fix, which systematically locates identical bug instances to prevent regressions and ensure codebase consistency.

Can I infer a bug pattern from recent code edits instead of describing it manually?

Yes, you can infer a bug pattern from recent edits. The scan supports two workflows: manually describing the target anti-pattern or automatically inferring the pattern from your most recent code fixes before searching the project.

Does this bug pattern scan work with multi-file software projects?

Yes, the bug pattern scan works with multi-file software projects. It applies pattern matching across the entire codebase to identify anti-patterns and outputs a date-stamped Markdown document under the research directory.

How are the findings from a codebase bug scan reported?

Findings from a codebase bug scan are reported in a structured Markdown document. The report is automatically saved to a date-stamped file under the .agents/research directory for easy tracking and review.