agentleFS
Sign inStart free
dcs-sonidcs-soni/skills/stale-todo-finder/SKILL.md

finding-stale-todos

Skill1 starsChanged 10 months agoMITView on GitHub

Find forgotten TODO/FIXME/HACK comments and track their age using git blame. Copy this checklist: Find all TODO-style comments in the codebase: Patterns detected: Correlate TODOs with git history: Output includes: TODOs are grouped into staleness buckets: Create actionable markdown report: Report includes: User: "Find forgotten TODOs in this project" Sample output: Filter by patterns or paths:

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Commit date when TODO was added

    line 58
  2. Distinctive:

    Create actionable markdown report:

    line 76
  3. Very specific:

    Run find_todos.py . → Finds 47 TODOs

    line 106
  4. Very specific:

    Run analyze_staleness.py .

    line 107
  5. Very specific:

    Run generate_report.py . → Creates report with:

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stale TODO Finder

Find forgotten TODO/FIXME/HACK comments and track their age using git blame.

Quick Start

Copy this checklist:

Stale TODO Analysis:
- [ ] Step 1: Scan for TODO comments
- [ ] Step 2: Analyze staleness with git blame
- [ ] Step 3: Categorize by age
- [ ] Step 4: Generate actionable report

Workflow

Step 1: Scan for TODO Comments

Find all TODO-style comments in the codebase:

python scripts/find_todos.py <directory> --format json

Patterns detected:

  • TODO, FIXME, HACK, XXX, BUG, OPTIMIZE
  • Works across Python, JavaScript, TypeScript, Go, Java, C/C++, Ruby, Rust

Step 2: Analyze Staleness

Correlate TODOs with git history:

python scripts/analyze_staleness.py <directory> --min-age 90

Output includes:

  • Commit date when TODO was added
  • Age in days
  • Original author
  • File and line number

Step 3: Categorize by Age

TODOs are grouped into staleness buckets:

CategoryAgePriority
🔴 Ancient>1 yearHigh - likely forgotten
🟠 Stale6-12 monthsMedium - needs review
🟡 Aging3-6 monthsLow - monitor
🟢 Recent<3 monthsOK - still relevant

Step 4: Generate Report

Create actionable markdown report:

python scripts/generate_report.py <directory> --output stale_todos.md

Report includes:

  • Summary statistics
  • TODOs sorted by age (oldest first)
  • Grouped by category
  • Author attribution

Utility Scripts

ScriptPurpose
find_todos.pyFind all TODO comments
analyze_staleness.pyGit blame analysis
generate_report.pyGenerate markdown report
generate_html_report.pyGenerate interactive HTML report

Example

User: "Find forgotten TODOs in this project"

  1. Run find_todos.py . → Finds 47 TODOs
  2. Run analyze_staleness.py . → 12 are older than 1 year
  3. Run generate_report.py . → Creates report with:
    • 12 ancient TODOs (>1 year)
    • 8 stale TODOs (6-12 months)
    • 27 recent TODOs (<6 months)

Sample output:

## 🔴 Ancient TODOs (>1 year) - 12 found

| File         | Line | Age      | Author | Content                  |
| ------------ | ---- | -------- | ------ | ------------------------ |
| src/utils.py | 42   | 847 days | @alice | TODO: optimize this loop |
| lib/auth.js  | 156  | 623 days | @bob   | FIXME: handle edge case  |

Configuration

Filter by patterns or paths:

# Only FIXME and BUG
python scripts/find_todos.py . --patterns FIXME,BUG

# Exclude vendor directories
python scripts/find_todos.py . --exclude "vendor/*,node_modules/*"

# Only show TODOs older than 6 months
python scripts/analyze_staleness.py . --min-age 180

Related Skills

  • codebase-onboarding — Understand codebase before cleanup
  • incident-response-helper — Some TODOs may be related to incidents

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free