From brooks-lint
Identifies, classifies, and prioritizes tech debt and maintainability problems using principles from twelve classic engineering books to build refactoring roadmaps.
npx claudepluginhub hyhmrright/brooks-lint --plugin brooks-lintThis skill uses the workspace's default tool permissions.
1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
Identifies, categorizes, and prioritizes technical debt across code, architecture, tests, dependencies, docs, and infrastructure. Scores by impact, risk, effort; outputs remediation plans.
Identifies, quantifies, and prioritizes technical debt in codebases across code complexity, architecture flaws, testing gaps, documentation lacks, and infrastructure issues. Creates remediation plans.
Analyzes codebases to identify, quantify, prioritize technical debt in code, architecture, testing, docs, and infra, with remediation plans.
Share bugs, ideas, or general feedback.
../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs../_shared/decay-risks.md for symptom definitions and source attributionsdebt-guide.md in this directory for the debt classification frameworkIf the user has not described the codebase or pointed to specific areas: apply Auto
Scope Detection from ../_shared/common.md to determine the assessment scope before proceeding.
Mode line in report: Tech Debt Assessment