brooks-sweep
Helps your agent analyze and fix various code quality aspects automatically. It applies safe fixes and asks for confirmation on riskier ones.
What it does
This tool analyzes your code for issues like decay, poor architecture, technical debt, and test failures. It attempts to automatically fix simpler problems and asks for your permission to fix more complex ones.
When to use it
- ✓When your code is becoming difficult to understand or maintain.
- ✓Before adding significant new features.
- ✓If you suspect there are many hidden errors in the code.
Example of what to ask your AI
“Please analyze and fix my code for quality issues.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool checks your code in four areas: overall quality, tests, technical debt, and audit. It automatically applies safe fixes and asks for your approval for riskier ones, always verifying that the fixes work.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill brooks-sweepOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/brooks-sweep/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Brooks-Lint — Full Sweep & Auto-Fix
When to Use
Use this skill when you need full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic...
Setup
- Read
../_shared/common.mdfor the Iron Law, Project Config, Report Template, and Health Score rules - Read
../_shared/source-coverage.mdfor book-level coverage, exceptions, and tradeoffs - Read
../_shared/decay-risks.mdfor production risk symptom definitions - Read
../_shared/test-decay-risks.mdfor test risk symptom definitions - Read
sweep-guide.mdin this directory for the unified scan and fix process
Process
If the user has not specified a project or directory: apply Auto Scope Detection
from ../_shared/common.md to determine the review scope before proceeding.
- Show pre-flight consent notice and wait for the user's one-time approval (Step 0 of the guide)
- Enumerate scope and initialize the
unresolvable/non_critical_rounds/fix_logstate (Step 1 of the guide) - Run the four dimensions in sequence — review, test, debt, audit — each scanning, classifying, applying Safe + Extended-Safe fixes, and verifying via the project test command (Steps 2–5 of the guide)
- Iterate: re-scan modified files + same-module + static consumers; converge on a clean round, retire 3-retry failures to the
unresolvableset, cap non-critical rounds at 3 (Step 6 of the guide) - Aggregate residual and unresolvable items and output the Full Sweep Report (Steps 7–8 of the guide)
Mode line in report: Full Sweep
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
FAQ
What are 'safe changes' and 'risky changes'?
Safe changes are those the tool is highly confident won't break the code. Risky changes are those that might have a larger impact, so they ask for your permission before being applied.
What happens if the tool can't fix an issue?
Issues that couldn't be automatically resolved are logged for you to review later.
Do I need to approve every fix?
No, only fixes considered risky. Safe ones are applied automatically.
Details
Original description by the author
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution.
Popularity
- GitHub stars
- 48k
- Ranking position
- #2449
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
cpp-testing
Makes your agent write and improve tests for C++ code. It helps set up testing tools and fix errors.
affaan-m/ECC
csharp-testing
Helps your agent create tests for C# and .NET code. It uses best practices to ensure tests are efficient and reliable.
affaan-m/ECC
django-tdd
Enables your agent to apply testing strategies for Django with pytest-django and TDD. It's useful for writing robust tests and ensuring code quality, especially for DRF APIs.
affaan-m/ECC