Brooks Sweep

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.agents/skills/_shared

.agents/skills/brooks-audit

.agents/skills/brooks-debt

.agents/skills/brooks-health

.agents/skills/brooks-review

Audit 0.4.1 · source sha 88b8bd892d5d · 25 Oct 2026Report an issue or request a re-scan

• Publisherhyhmrright GitHub userOwner of the repository this skill is read from
• Source folderhyhmrright/brooks-lint/skills/brooks-sweepThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict88b8bd892d5dA new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: brooks-sweep
description: >
  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 code changes; single-dimension reviews (use the focused skill
  instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health
  checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.
metadata:
  opencode/slash: "true"
---

# 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`

Excerpt, first 2,030 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/hyhmrright/brooks-lint
git -C brooks-lint checkout 88b8bd892d5d

Works in

1. 2026-10-25
   !CAUTION B 89 / 100

   first audit · source 88b8bd892d5d

Questions about Brooks Sweep

• github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-sweep — the audited source at commit 88b8bd892d5d and every finding aboveObserved · 25 Oct 2026

Spotted something wrong? Report a correction · Methodology