sweeper

Identify and catalog bug or anti-pattern occurrences across a software repository.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/strawgate/agent-skills --skill sweeper-strawgate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sweeper
Source: https://github.com/strawgate/agent-skills/tree/main/sweeper
Command: npx skills add https://github.com/strawgate/agent-skills --skill sweeper-strawgate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent code quality by identifying every single instance of a specific bug or anti-pattern across an entire codebase, ensuring no occurrences are missed during refactoring.

Core Features & Use Cases

  • Exhaustive Search: Scans the entire repository to find every occurrence of a defined pattern, rather than just providing a sample.
  • Comprehensive Reporting: Generates a structured report including file paths, line numbers, and recommended fix patterns.
  • Use Case: Use this when you need to perform a large-scale cleanup, such as identifying all missing error handling in asynchronous functions or locating deprecated API usage across a legacy project.

Quick Start

Use the sweeper skill to find all instances of unhandled promise rejections in the current codebase and generate a report.

Frequently Asked Questions about sweeper

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

FAQPage Schema
How do I find every occurrence of an anti-pattern across a codebase for refactoring?

To find every occurrence of an anti-pattern across a codebase, you can use an exhaustive static-analysis audit that scans the entire repository and catalogs each instance with precise file locations and remediation strategies.

What is the best way to audit technical debt in a legacy project?

Auditing technical debt in a legacy project involves exhaustively scanning the repository to identify and catalog specific bugs or deprecated API usage, generating a structured report with file paths, line numbers, and recommended fix patterns.

How do I locate all missing error handling in asynchronous functions?

To locate all missing error handling in asynchronous functions, perform an exhaustive codebase search using grep and static-analysis tools to identify unhandled promise rejections and catalog them for large-scale code refactoring.

Can I get a structured report with line numbers for bug-hunting?

Yes, comprehensive bug-hunting generates a structured report including exact file paths, line numbers, and recommended fix patterns to facilitate large-scale code refactoring and ensure exhaustive coverage of technical debt.

Does exhaustive codebase static-analysis work for large-scale cleanup tasks?

Exhaustive codebase static-analysis works for large-scale cleanup tasks by scanning the entire repository to find every occurrence of a defined pattern rather than just providing a sample, ensuring no instances are missed during refactoring.

Why should I use an exhaustive code audit instead of manual bug-hunting?

An exhaustive code audit prevents inconsistent code quality by ensuring every single instance of a specific bug or anti-pattern is identified across an entire codebase, eliminating the risk of missed occurrences inherent in manual bug-hunting.