hyhmrright/brooks-lint

Brooks Audit maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Use it for architecture audits or to give new developers a codebase tour.

Brooks Debt identifies, classifies, and prioritizes maintainability problems and builds a refactoring roadmap using twelve classic engineering books. Use it to plan what to clean up first or justify refactoring to management.

Brooks Harness orchestrates maintenance work on the brooks-lint plugin itself, running a sequential pipeline of skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, and release-manager agents. Use it when a maintainer asks to add or edit skills, refresh evals, sync docs, audit trigger boundaries, or release brooks-lint.

Brooks Health scores a project across four quality dimensions—PR quality, architecture, tech debt, and test quality—in a single pass, drawing on twelve classic engineering books. Use it for an overall quality assessment before a release or team onboarding.

Brooks Lint Release cuts a brooks-lint release: it sets the package.json version, propagates it across plugin manifests and docs, writes the changelog, validates, commits, tags, and publishes. Use it when the maintainer asks to release, cut a release, or ship a new version.

Brooks Lint Skill Scaffold creates the files for a new brooks-lint analysis skill—SKILL.md, guide, and eval scenarios—so it passes npm run validate and npm run evals the first time. Maintainers use it when adding a new skill to the brooks-lint plugin.

Brooks Review performs PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Use it when reviewing a PR, diff, or pasted code for readiness to merge or refactoring feedback.

Brooks Sweep runs a unified analysis across code decay, architecture, tech debt, and test quality, then applies fixes directly to the codebase. Use it when asked to sweep the codebase, fix everything, auto-fix all issues, or clean up the whole project in one command.

Brooks Test reviews an existing test suite for structural quality problems—brittleness, mock abuse, coverage illusions, slow execution, and poor readability—using principles from classic engineering books. Use it when tests keep breaking, take forever, or pass while bugs reach production.