todo-finder_skill

Overview

This skill finds and organizes TODO, FIXME, HACK, NOTE, and related action-item comments across a TypeScript codebase. It scans files, groups findings by priority, and returns a clear, actionable summary with file paths and line numbers. Use it to surface technical debt, bugs, and improvement opportunities quickly.

How this skill works

The skill searches the repository for common markers (TODO, FIXME, HACK, BUG, NOTE, XXX, OPTIMIZE, REFACTOR, etc.) using recursive text search patterns. It classifies each match into Critical, Important, or Informational buckets, records file paths and line numbers, and can include surrounding context. Results are formatted as a prioritized list with counts and suggested next steps.

When to use it

• You want a quick inventory of outstanding work or technical debt
• You need to prepare a backlog of actionable items from code comments
• You want to triage critical fixes (FIXME/BUG) before a release
• You need to audit temporary workarounds or HACKs
• You want contextual evidence for code review or planning sessions

Best practices

• Search all relevant file types (.ts, .tsx, .js, .jsx, .py, .java, markdown) and include tests and docs
• Group results by priority: Critical (FIXME, BUG), Important (TODO, HACK), Informational (NOTE, OPTIMIZE, REFACTOR)
• Show file path and line number for every item so reviewers can jump directly to code
• Include a short code context snippet where helpful to clarify the issue
• If results are numerous, filter by folder, file type, or marker to focus work

Example use cases

• "Find all TODOs in this project" — returns a summarized list with file:line and counts
• "Show me all FIXMEs" — lists critical items first for immediate triage
• "List action items in the authentication module" — searches a specific folder and groups by priority
• "Show HACKs and temporary fixes" — highlights areas that need proper implementation
• "Scan repo before release to find critical BUG/FIXME comments" — quick pre-release triage