brooks-sweep
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 engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without co
npx skills add hyhmrright/brooks-lint --skill brooks-sweep --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Brooks-Lint — Full Sweep & Auto-Fix ## Setup Read in order: 1. `../_shared/common.md` — Iron Law, Project Config, Report Template, Health Score 2. `../_shared/source-coverage.md` — book coverage, exceptions, tradeoffs 3. `../_shared/decay-risks.md` — production risk symptoms 4. `../_shared/test-decay-risks.md` — test risk symptoms 5. `sweep-guide.md` (this directory) — the unified scan and fix process ## Process **Scope:** if the user did not specify a project or directory, apply Auto Scope Detection (`../_shared/common.md`) first. 1. Show the pre-flight consent notice and wait for one-time approval (Step 0 of the guide) 2. Enumerate scope and initialize pipeline state (Step 1 of the guide) 3. Run the four dimensions in sequence — review, test, debt, audit — each scanning, classifying, fixing, and verifying (Steps 2–5 of the guide) 4. Iterate over modified files and their consumers until a clean round or the cap (Step 6 of the guide) 5. Aggregate residual and unresolvable items and output the Full Sweep Report (Steps 7–8 of the guide) **Mode line in report:** `Full Sweep`
- Setup
- Process
What does the brooks-sweep skill do?
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 engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without co
How do I install it?
Run `npx skills add hyhmrright/brooks-lint --skill brooks-sweep --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hyhmrright/brooks-lint, a repository with 1,284 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.