Document and prioritize technical debt. Use when the user says "tech debt", "legacy code", "this code is a mess", "refactoring plan", "we need to clean this up", "paying down debt", "this is hard to change", "how do we fix this codebase", or has code that's difficult to understand or modify - even if they don't explicitly say "technical debt".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview
Based on **"Working Effectively with Legacy Code"** by Michael Feathers. Feathers' definition: legacy code is code without tests. His central technique: find the "seams" - places where you can insert test coverage without changing the code under test. Once a seam has test coverage, you can safely refactor. The discipline: never refactor without a safety net. Never add features to untested code without first covering it.
## Workflow
### Step 1: Define the debt
Before prioritizing, describe the debt specifically:
```
Debt item: [name]
Location: [file:line or module]
What it is: [one sentence description]
Why it's a problem: [what it makes harder]
Symptom: [what developers experience because of it]
```
Vague debt ("the codebase is messy") can't be prioritized. Specific debt can.
### Step 2: Classify the debt type
| Type | Description | Urgency |
|------|-------------|---------|
| **Reckless/Deliberate** | Shortcuts taken knowingly ("we'll fix it later") | High |
| **Reckless/Inadvertent** | Mistakes made without knowing better | High |
| **Prudent/Deliberate** | Conscious tradeoff: ship now, fix later | Medium |
…
The line at the top of this page pins the label git:20260303.09b1726, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_2rbih4p6ujqph2yo
GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/tech-debt
GET https://markdownregistry.com/api/v1/blob/24429394645639508eb3b02b76e43e106c16def1c4f7d290332490a500dde46e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
qa-aman/claude-skills · .claude/skills/create-skill/SKILL.md · Create or update Claude Code skills following Anthropic's official skill standard. Use when user says "create a skill"…
qa-aman/claude-skills · .claude/skills/sync-skills/SKILL.md · Fetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when…
qa-aman/claude-skills · skills/by-role/accountant/audit-workpaper/SKILL.md · Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says…
qa-aman/claude-skills · skills/by-role/accountant/budget-variance-analysis/SKILL.md · Analyze budget vs. actual variances, identify root causes, and recommend corrective actions. Use when an accountant or…
qa-aman/claude-skills · skills/by-role/accountant/financial-statement-review/SKILL.md · Analyze and interpret financial statements to surface performance signals, quality concerns, and red flags. Use when an…
qa-aman/claude-skills · skills/by-role/accountant/month-end-close/SKILL.md · Run, document, or review a structured month-end close process. Use when an accountant says "help me with month-end…
qa-aman/claude-skills · skills/by-role/accountant/tax-position-memo/SKILL.md · Write a technical tax position memo that documents a tax filing position with authorities, facts, analysis, and…
qa-aman/claude-skills · skills/by-role/business-analyst/acceptance-criteria-writer/SKILL.md · Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance…
qa-aman/claude-skills · skills/by-role/business-analyst/brd-writer/SKILL.md · Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the…
qa-aman/claude-skills · skills/by-role/business-analyst/cost-benefit-analysis/SKILL.md · Build a business case with costs, benefits, and ROI. Use when the user says "cost-benefit analysis", "business case"…
qa-aman/claude-skills · skills/by-role/business-analyst/data-dictionary/SKILL.md · Generate a data dictionary documenting entities, fields, and business rules. Use when the user says "data dictionary"…
secondsky/claude-skills · plugins/tech-debt/skills/tech-debt/SKILL.md · Use when reworking a change to prevent tech debt, or auditing existing debt to categorize, score, and prioritize the…
striderza/opencodegamestudios · .agents/modules/stories/skills/tech-debt/SKILL.md · Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt…
striderza/opencodegamestudios · .agents/skills/tech-debt/SKILL.md · Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt…
furkantokkan/agent-foundry · plugins/agent-foundry/skills/tech-debt/SKILL.md · Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt…
pantheon-org/tekhne · skills/project-mgmt/tech-debt/SKILL.md · Maintain docs/TECH_DEBT.md, the living list of code-level cleanup that isn't a risk, a shortcut, or an open decision…