agentsclimarketplace

Stale todo finder

Skill dcs-soni/skills/stale-todo-finder

A collection of custom Claude Code Skills to supercharge your development workflow.

Install
npx -y skills add dcs-soni/skills --skill stale-todo-finder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.6 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.