Tech Debt Cleanup
Structured workflow for addressing accumulated technical debt
CLAUDE.md
When addressing technical debt:
- Identify the debt: scan for TODO/FIXME comments, skipped tests, known workarounds, and suppressed warnings.
- Prioritize by impact: what debt causes the most bugs, slows development the most, or blocks future work?
- Address one piece of debt per PR. Don’t bundle unrelated cleanups.
- Add or fix tests before cleaning up the code.
- Clean up the code. Remove workarounds, fix the underlying issue, update patterns to current standards.
- Run the full test suite to verify no regressions.
- Remove the TODO/FIXME comment when the debt is resolved.
Copy this workflow into your CLAUDE.md or agent config file so your agent follows this process automatically.