brooks-debt
installsforks
How to install brooks-debt?
hyhmrright/brooks-lint/brooks-debt
$npx -y skills add hyhmrright/brooks-lint --skill brooks-debtTech 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
SKILL.md
| 1 | # Brooks-Lint — Tech Debt Assessment |
| 2 | |
| 3 | ## Setup |
| 4 | |
| 5 | 1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules |
| 6 | 2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs |
| 7 | 3. Read `../_shared/decay-risks.md` for symptom definitions and source attributions |
| 8 | 4. Read `debt-guide.md` in this directory for the debt classification framework |
| 9 | |
| 10 | ## Process |
| 11 | |
| 12 | **If the user has not described the codebase or pointed to specific areas:** apply Auto |
| 13 | Scope Detection from `../_shared/common.md` to determine the assessment scope before proceeding. |
| 14 | |
| 15 | 1. Scan for all six decay risks (Step 1 of the guide); list every finding before scoring |
| 16 | 2. Apply the Pain × Spread priority formula and classify debt intent (Steps 2–3 of the guide) |
| 17 | 3. Group findings by decay risk (Step 4 of the guide) |
| 18 | 4. Output using the Report Template from common.md, plus the Debt Summary Table |
| 19 | |
| 20 | **Mode line in report:** `Tech Debt Assessment` |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
