Ask Claude to Find, Prioritize, and Resolve Every TODO in Your Codebase
TODO comments are promises to your future self that rarely get kept. They accumulate in every codebase — some are critical reminders about incomplete work, others are three-year-old notes about refactors that never happened. Claude Code can audit them all and help you clear the backlog.
Find all TODO, FIXME, HACK, and XXX comments in the codebase.
Group them by priority: which ones are blocking or risky, which are
nice-to-have, and which are obsolete and should just be removed.
Claude searches every file, reads the context around each comment, and categorises them:
CRITICAL (fix these now):
- src/billing/charge.ts:42 — FIXME: race condition when two charges fire simultaneously
- src/auth/session.ts:18 — TODO: validate refresh token expiry (currently accepts expired tokens)
SHOULD FIX (schedule these):
- src/api/orders.ts:156 — TODO: add pagination (currently loads all orders)
- src/utils/date.ts:8 — HACK: timezone offset hardcoded to UTC-5
OBSOLETE (remove these):
- src/legacy/importer.ts:23 — TODO: migrate to new API (migration was completed 6 months ago)
- src/config/db.ts:5 — FIXME: switch to connection pooling (already using pooling)
Then ask Claude to resolve the straightforward ones:
Fix the critical TODOs and the obsolete ones. For the critical issues,
implement the actual fix. For the obsolete ones, just remove the comments.
Leave the scheduled items as TODOs but add a date and owner.
You can also set up a CLAUDE.md rule for ongoing management:
# In CLAUDE.md
When adding TODO comments, always include: the author, the date,
and a brief explanation of why it can't be done now.
Format: // TODO(@username 2025-03-29): reason
TODOs without a plan are just noise — let Claude audit them, resolve the easy ones, and turn the rest into actionable items.
via Claude Code
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.