Claude skill
Brooks Debt
Brooks Debt is a Claude skill in the Brooks Lint plugin. Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books.
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.
The skill's instructions (about 133 words) cover:
- Setup
- Process
How to use it
- Brooks Debt comes inside the Brooks Lint plugin, so you get it by installing that plugin, along with its 5 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose brooks-debt. In Claude Code and Cowork, type:/brooks-lint:brooks-debt
Source
- Plugin
- Brooks Lint
- SKILL.md
- View on GitHub
- Repo stars
- 1,578
- Repo last pushed
- Nov 16, 2026
- Checked
- Nov 16, 2026
More skills in Brooks Lint
- Brooks HealthCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic…
- Brooks ReviewPR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books.
- 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.
- Brooks TestTest quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy…
- Brooks AuditArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.