skills.rest
manastalukdar
manastalukdarCOMMUNITY
Explore all skills by this author →
Website𝕏@manastalukdarGitHub

fix-todos

Resolve TODO, FIXME, HACK, and XXX comments using context-aware strategies.

1|Updated Jan 26, 2026
Search Tags:#code quality#automation#developer tools#refactoring#technical debt#todo
One-click install
npx skills add https://github.com/manastalukdar/claude-devstudio --skill fix-todos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-todos
Source: https://github.com/manastalukdar/claude-devstudio/tree/main/skills/fix-todos
Command: npx skills add https://github.com/manastalukdar/claude-devstudio --skill fix-todos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of finding and resolving TODO, FIXME, HACK, and XXX comments within your codebase, ensuring that outstanding tasks are systematically addressed.

Core Features & Use Cases

  • Automated TODO Discovery: Scans your codebase to identify all TODO-style comments.
  • Context-Aware Resolution: Intelligently resolves TODOs based on your project's coding patterns and context.
  • Session Continuity: Maintains progress across multiple sessions, allowing you to resume work seamlessly.
  • Use Case: You've inherited a large codebase with numerous TODO comments. This Skill can systematically go through them, suggest resolutions based on existing code patterns, and help you clear technical debt efficiently.

Quick Start

Run the fix-todos skill to start resolving all TODO comments in the current project.

Frequently Asked Questions about fix-todos

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

FAQPage Schema
How do I automatically resolve TODO and FIXME comments in my codebase?▼

Automated TODO resolution works by scanning your codebase with grep to identify TODO, FIXME, HACK, and XXX comments, then applying context-aware strategies to systematically plan and implement fixes based on your project's existing coding patterns.

What is the best way to clear technical debt from inherited TODO comments?▼

Clearing technical debt from inherited TODO comments requires systematically identifying outstanding tasks via codebase scans, then intelligently resolving them based on your project's specific context to ensure tasks are addressed efficiently.

Can I resume fixing TODO comments across multiple development sessions?▼

Yes, you can resume fixing TODO comments across multiple sessions because the process maintains session-based state tracking via JSON and Markdown files, allowing you to seamlessly resume your code maintenance and refactoring workflows.

Do I need grep to find and fix TODO comments in my project?▼

Yes, you need grep for efficient discovery of TODO, FIXME, HACK, and XXX comments within your codebase, as it is required to systematically identify outstanding tasks before applying context-aware resolution strategies.

How does context-aware resolution handle different coding patterns when fixing TODOs?▼

Context-aware resolution handles different coding patterns by analyzing your project's existing code structure and conventions, then intelligently planning and implementing fixes that align with your specific refactoring workflows and technical context.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced
guccangguccang
3

test-driven-development

Create failing tests before implementing minimal production code.

Community
Intermediate
richardnguyen0715richardnguyen0715

code-review-and-quality

Automate code review against correctness, readability, architecture, security, and performance criteria.

Community
Advanced
danfrdndanfrdn

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Community
Advanced