Receber por email
← Voltar para o catálogo

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 th

1.2kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add hyhmrright/brooks-lint

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/brooks-sweep/svg)](https://www.skillteca.com.br/skills/brooks-sweep)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Brooks-Lint — Full Sweep & Auto-Fix

Setup

  1. Read ../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules
  2. Read ../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs
  3. Read ../_shared/decay-risks.md for production risk symptom definitions
  4. Read ../_shared/test-decay-risks.md for test risk symptom definitions
  5. Read sweep-guide.md in 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.

  1. Show pre-flight consent notice and wait for the user's one-time approval (Step 0 of the guide)
  2. Enumerate scope and initialize the unresolvable / non_critical_rounds / fix_log state (Step 1 of the guide)
  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)
  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)
  5. Aggregate residual and unresolvable items and output the Full Sweep Report (Steps 7–8 of the guide)

Mode line in report: Full Sweep

Compartilhar X LinkedIn