New to Claude Skills? Learn how to install them →

Bsickn33 on GitHub

Brooks-Lint

Free

Comprehensive code quality analysis and auto-fixing.

Get this skill

Free · Opens the source repo

What Brooks-Lint does

Brooks-Lint is a developer tool designed to perform a thorough analysis of your codebase across multiple quality dimensions, including code decay, architecture, technical debt, and test quality. It operates in a full-sweep mode that not only identifies issues but also applies fixes directly to the codebase. The tool intelligently differentiates between safe changes, which are applied automatically, and risky changes, which require user confirmation before execution. This ensures that developers can maintain control over the modifications made to their projects while benefiting from automated improvements.

The skill is particularly useful for teams looking to enhance their code quality without extensive manual intervention. By following a structured process, Brooks-Lint first determines the scope of the review, then runs a series of scans to identify and classify issues. It applies fixes in a systematic manner, iterating over the code until a clean round is achieved. The final output is a comprehensive Full Sweep Report that details the modifications made and any residual issues that require further attention.

To set up Brooks-Lint, users are guided through a series of preparatory steps, including reading relevant documentation and understanding the project's context. The skill emphasizes safety and reliability; users are advised to verify commands and generated code before applying any changes. This makes it suitable for developers who need to ensure that their code remains stable and maintainable while addressing quality concerns.

Overall, Brooks-Lint is an effective tool for developers who want to automate the process of code quality assessment and remediation, allowing them to focus on higher-level tasks while ensuring their codebase remains healthy and up to standard.

When to use it

Use Brooks-Lint when you need a comprehensive analysis of your codebase's quality and want to apply fixes automatically.

When not to use it

Avoid using this skill for projects where the context is unclear or where manual review and approval of changes are critical.

What you can build with it

Codebase Quality Assessment

Use Brooks-Lint to perform a comprehensive quality assessment of your codebase before a major release.

Technical Debt Reduction

Employ the tool to identify and remediate technical debt quickly, improving long-term maintainability.

Test Quality Improvement

Run Brooks-Lint to enhance the quality of your tests, ensuring better coverage and reliability.

How to install Brooks-Lint

View source

1. Install with the skills CLI

npx skills add sickn33/agentic-awesome-skills/brooks-sweep --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by sickn33

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

  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

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.

Frequently asked questions about Brooks-Lint

Similar skills