AI Blocks › Build and ship software
Monthly technical debt review
Point it at your code each month. Get new debt found, last month's clean-up checked and the next small fixes ranked.
Monthly technical debt review is a free AI agent for the job "Build and ship software". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks
What it does
Debt in code grows quietly. A clean-up gets agreed, does not get done, or gets done and changes nothing. A month later nobody can say whether the code is better or worse, so the same complaints come back. This agent keeps a dated list so it can answer that. Each month it scans, compares with the last scan and checks every fix you agreed to. A fix that landed but left the debt in place is marked, so you do not repeat it. When many items sit in one area, it looks for the design cause first. It hands back at most five fixes, each cut into steps small enough to review alone.
You give it
- The code, as a folder or repo the AI can open
- How many people work on it and how many days a month can go to clean-up (optional)
- The parts that hurt most (optional)
- Last month's folder, after the first run
- Your question (optional)
- A draft (optional)
You get
- New, gone and still-open debt against last month, with the counts
- A check of each fix you agreed to last time, marked done, did not work or not started
- Up to five fixes to approve, each cut into small reviewable steps
- A design cause, when many items share one area
Use it when
- You work in a codebase that gets slower to change each quarter.
- You agree clean-up work in planning but never see whether it helped.
- One person is the only one who understands a part of the code.
How to use it
- Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to run this month's check.
- Open it in the folder with your code. The first run builds the base list.
- Read the fixes. Say yes to the ones you want, and it records them for next month.
- Make the fixes in your normal way, or say yes to one and let it make only that change on its own branch.
- Run it again next month. It checks whether the fixes worked.