brooks-debt

Featured

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.

Code & Development 1,469 stars 66 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Brooks-Lint — Tech Debt Assessment ## 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` — symptom definitions and source attributions 4. `debt-guide.md` (this directory) — the debt classification framework ## Process **Scope:** if the user did not describe the codebase or point to specific areas, apply Auto Scope Detection (`../_shared/common.md`) first. 1. Scan for all six decay risks (Step 1 of the guide); list every finding before scoring 2. Apply the Pain × Spread priority formula and classify debt intent (Steps 2–3 of the guide) 3. Group findings by decay risk (Step 4 of the guide) 4. Output using the Report Template from common.md, plus the Debt Summary Table **Mode line in report:** `Tech Debt Assessment`

Details

Author: hyhmrright
Repository: hyhmrright/brooks-lint
Created: 5 months ago
Last Updated: 4 days ago
Language: JavaScript
License: MIT

Integrates with

Kubernetes · Infrastructure

Bundled in these plugins

brooks-lint

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

tech-debt-audit

Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, LSP, and language-native tooling. Produces TECH_DEBT_AUDIT.md with severity, effort estimates, and prioritized fixes. Use when asked for codebase health check, tech debt audit, architecture review, code quality assessment, or cleanup planning. Triggers: 'tech debt', 'technical debt', 'debt audit', 'code health', 'technical debt audit', 'codebase health check', 'find tech debt', 'debt analysis', 'audit code quality'.

68,941 Updated today

code-yeongyu

Code & Development Featured

assess-technical-debt

Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", or "what's our worst code". Analysis-only — does not modify code.

402 Updated 2 days ago

tobihagemann

AI & Automation Listed

tech-debt-tracker

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

1 Updated today

nariatrip191