Stats
Actions
Tags
From brooks-lint
Scores a project across PR quality, architecture, tech debt, and test quality in a single pass, drawing on twelve classic engineering books. Useful for big-picture codebase health assessments before releases or when onboarding a team.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brooks-lint:brooks-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
../_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 production risk symptom definitions../_shared/test-decay-risks.md for test risk symptom definitionshealth-guide.md in this directory for the dashboard orchestration processIf the user has not specified a project or directory: apply Auto Scope Detection
from ../_shared/common.md to determine the review scope before proceeding.
Mode line in report: Health Dashboard
npx claudepluginhub hyhmrright/brooks-lint --plugin brooks-lintConducts full codebase health audit across architecture, security, code quality, dependencies, test coverage. Produces scored report with letter grades and prioritized remediation. Use for existing codebases or before releases.
Generates health scores for JS/TS projects assessing architecture conformance, test coverage, security risks, performance metrics, and maintainability. Use for onboarding, quality checks, or refactoring baselines.
Analyzes codebase complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan for legacy projects or external repo evaluation.