todo-resolver

Discover and triage TODO, FIXME, and HACK comments across a repository.

20|1|Updated Feb 6, 2026

Search Tags:#refactor #todo #static-analysis #triage #code-maintenance

Ready to run

npx skills add https://github.com/BrOrlandi/my-claude-skills --skill todo-resolver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: todo-resolver
Source: https://github.com/BrOrlandi/my-claude-skills/tree/main/todo-resolver
Command: npx skills add https://github.com/BrOrlandi/my-claude-skills --skill todo-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unresolved TODO, FIXME, and HACK comments accumulate in codebases, increasing technical debt and slowing development. This Skill helps locate these annotations, analyze their potential impact and complexity, and optionally guide or implement resolutions to maintain code health.

Core Features & Use Cases

Automated discovery of TODO/FIXME/HACK comments across a repository
Impact analysis, triage, and optional change planning to address debt items
Contextual reference gathering and prioritization to inform development work

Quick Start

Run the TODO resolver against your repository to discover, triage, and plan resolutions for TODO/FIXME/HACK items.

Frequently Asked Questions about todo-resolver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find and triage TODO comments across my codebase?▼

To triage TODO comments across your codebase, this Skill performs grep-like scanning to identify TODO, FIXME, and HACK annotations, then analyzes their context and impact to produce structured findings for maintenance review.

What is the best way to assess the impact of FIXME comments before refactoring?▼

Assessing the impact of FIXME comments requires contextual reference gathering and repository parsing. This Skill evaluates surrounding code relationships to determine technical debt complexity and inform maintenance prioritization.

Can I scope code maintenance searches to specific directories or files?▼

Yes, you can scope code maintenance searches to specific directories. This Skill supports scoped searches to target particular areas of your repository, enabling focused triage and change planning for unresolved annotations.

How do I plan resolutions for accumulated technical debt from HACK comments?▼

Planning resolutions for accumulated technical debt from HACK comments involves gathering contextual references and prioritizing findings. This Skill provides impact assessment to guide optional change implementation and maintain code health.

Does this static analysis tool work without external dependencies?▼

Yes, this static analysis tool works without external dependencies. It relies on built-in repository parsing and grep-like scanning capabilities to discover and analyze TODO, FIXME, and HACK items independently.

When should I avoid automated TODO resolution during code maintenance?▼

Automated TODO resolution should be approached with caution when impact assessment reveals high complexity. This Skill produces structured findings to inform review, but direct implementation of changes requires careful evaluation of contextual dependencies.