One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill bug-sweep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-sweep
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/bug-sweep
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill bug-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bug-sweep Skill systematically hunts for bug patterns and code smells across a codebase, fixes anything AI-fixable within the current session, and defers genuinely blocked items to a backlog instead of wasting time on stale or unfixable findings.

Core Features & Use Cases

  • Stack-aware scanning and pattern selection: Detects the project’s language/tooling stack and selects appropriate bug patterns, including compiled/framework-heavy stacks via documentation verification.
  • Parallelized discovery with test execution: Runs fast mechanical grep first, then dispatches semantic analysis per code chunk and executes the test suite to confirm failures.
  • Triage, fixing, and backlog hygiene: Classifies findings into fix-now vs backlog, applies automated fixes with docs verification when configured, and prunes “already-fixed” backlog items using verified resolving SHAs.

Quick Start

Run bug-sweep scoped to a specific directory or the full repository to enumerate fixable issues and leave blocked items in the backlog.

Frequently Asked Questions about bug-sweep

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

FAQPage Schema
How do I systematically find and fix bug patterns across a codebase after a period of churn?▼

Static analysis and bug fixing across a codebase involves stack detection, chunked parallel analysis using mechanical grep and semantic agents, and test-suite execution to confirm failures before applying automated fixes and deferring blocked items to a backlog.

What is the best way to triage a large backlog of code smells and unfixable findings?▼

Backlog triage for code smells involves classifying findings into fix-now versus blocked items, applying automated fixes within the session, and pruning already-fixed backlog items using verified resolving SHAs to maintain backlog hygiene.

Does automated bug scanning work with compiled or framework-heavy tech stacks?▼

Automated bug scanning supports compiled or framework-heavy stacks by detecting the project's tooling, selecting appropriate bug patterns, and performing optional API and documentation verification to validate fixes.

Can I restrict codebase scanning to a specific directory instead of the full repository?▼

Codebase scanning can be restricted to a specific directory by providing a path argument, allowing you to scope the systematic hunt for bug patterns and code smells rather than running a full repository check.

How does chunked parallel review improve static analysis performance?▼

Chunked parallel review improves static analysis by running fast mechanical grep first, then dispatching semantic analysis agents per code chunk to comprehensively discover bug patterns across the codebase.

When should I use a comprehensive codebase sweep instead of a daily bug check?▼

A comprehensive codebase sweep is intended for periods of code churn where you need exhaustive coverage and backlog triage, rather than a routine daily check or single-bug cleanup for isolated issues.