brooks-sweep
installsforks
How to install brooks-sweep?
hyhmrright/brooks-lint/brooks-sweep
$npx -y skills add hyhmrright/brooks-lint --skill brooks-sweepFull-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 eng
SKILL.md
| 1 | # Brooks-Lint — Full Sweep & Auto-Fix |
| 2 | |
| 3 | ## Setup |
| 4 | |
| 5 | 1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules |
| 6 | 2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs |
| 7 | 3. Read `../_shared/decay-risks.md` for production risk symptom definitions |
| 8 | 4. Read `../_shared/test-decay-risks.md` for test risk symptom definitions |
| 9 | 5. Read `sweep-guide.md` in this directory for the unified scan and fix process |
| 10 | |
| 11 | ## Process |
| 12 | |
| 13 | **If the user has not specified a project or directory:** apply Auto Scope Detection |
| 14 | from `../_shared/common.md` to determine the review scope before proceeding. |
| 15 | |
| 16 | 1. Show pre-flight consent notice and wait for the user's one-time approval (Step 0 of the guide) |
| 17 | 2. Enumerate scope and initialize the `unresolvable` / `non_critical_rounds` / `fix_log` state (Step 1 of the guide) |
| 18 | 3. 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) |
| 19 | 4. Iterate: re-scan modified files + same-module + static consumers; converge on a clean round, retire 3-retry failures to the `unresolvable` set, cap non-critical rounds at 3 (Step 6 of the guide) |
| 20 | 5. Aggregate residual and unresolvable items and output the Full Sweep Report (Steps 7–8 of the guide) |
| 21 | |
| 22 | **Mode line in report:** `Full Sweep` |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
