Code Quality Tool

TODO Tracker

Find TODO, FIXME, HACK, and other markers across your codebase with priority classification and git blame for authorship.

Install

Get the CLI Tool

Run the TODO tracker locally as an MCP server, or try it online below.

npx @clinetools/todo-tracker
Requires Node.js 18+
  • 10 marker types — TODO, FIXME, HACK, XXX, BUG, WORKAROUND, OPTIMIZE, REFACTOR, DEPRECATED, NOTE
  • Priority classification — high, medium, and low severity levels
  • Git blame integration — see who wrote each marker and when
  • Multi-language support — JS, TS, Python, Go, Rust, Java, and more
  • Zero config — just run with npx
Tutorial

How to Use It

Three ways to track TODOs — pick the one that fits your workflow.

1

Try Online

Explore the interactive demo below to see TODO tracking in action on sample projects.

↓ Jump to interactive demo
2

Use via CLI

Run as a local MCP server and connect any MCP-compatible client.

npx @clinetools/todo-tracker
3

Add to Cline / Claude Code

Add the tool to your MCP settings for instant access from your AI assistant.

"todo-tracker": { "command": "npx", "args": ["@clinetools/todo-tracker"] }

MCP Client Configuration

{
  "mcpServers": {
    "todo-tracker": {
      "command": "npx",
      "args": ["@clinetools/todo-tracker"]
    }
  }
}

Example: Scan a Project

// Prompt to your AI agent:
"Find all TODOs and FIXMEs in my src/ directory"

// The agent calls:
find_todos({ path: "src/", include_blame: true })

// Output:
{
  "summary": {
    "filesScanned": 18,
    "totalMarkers": 12,
    "high": 4,
    "medium": 6,
    "low": 2
  },
  "items": [
    { "marker": "FIXME", "priority": "high", "text": "Race condition in auth flow",
      "file": "src/auth.ts", "line": 47, "author": "alice", "date": "2025-11-03" },
    { "marker": "TODO", "priority": "medium", "text": "Add pagination support",
      "file": "src/api.ts", "line": 23, "author": "bob", "date": "2026-01-15" }
  ]
}

Example: Pre-Release Audit

// Prompt to your AI agent:
"Find all FIXMEs and HACKs before we ship v2.0.
Flag anything older than 3 months as a red flag."

// The agent scans, groups by priority,
// highlights stale markers with git blame dates,
// and recommends which ones to resolve before release.
Live Demo

Try It Online

Select a sample project to see TODO markers found with priority levels and simulated git blame.

Select a project above

Analysis Results

Learn

Why TODO Tracking Matters

Untracked markers are invisible technical debt — tracked markers are manageable work items.

FIXME vs TODO

FIXME means broken code that works around a bug — it needs fixing before it causes problems. TODO means a planned improvement that can be scheduled. Knowing the difference determines what ships and what waits.

Technical Debt Visibility

Tracked TODOs are manageable debt — you know where they are, who wrote them, and how old they are. Untracked TODOs are hidden debt that compounds silently until something breaks in production.

Priority Triage

HACK, BUG, FIXME, and XXX are high priority — they indicate known problems. TODO, REFACTOR, OPTIMIZE, and WORKAROUND are medium. NOTE is low. Priority classification turns a flat list into an actionable queue.

Pre-Release Audits

Before shipping, scan for FIXMEs and HACKs. A FIXME in your payment flow or a HACK in your auth middleware is a time bomb. Catching these in a pre-release audit saves you from shipping known problems.

Ownership

Git blame shows who wrote each TODO and when. A TODO from last week is fine — a FIXME from 18 months ago is a red flag. Old markers indicate forgotten debt that nobody owns anymore and needs immediate attention.

Need Automated Technical Debt Tracking?

Our Pro plan includes scheduled scans with reports that surface stale TODOs and high-priority markers.

View Plans