aitodo

Resolve AITODO comments by implementing code changes and removing markers.

20|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/radareorg/radare2-skills --skill aitodo-radareorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aitodo
Source: https://github.com/radareorg/radare2-skills/tree/main/dev/aitodo
Command: npx skills add https://github.com/radareorg/radare2-skills --skill aitodo-radareorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you resolve engineering tasks described in AITODO comments by turning them into concrete code changes, then removing the outdated comments so the codebase stays clean and actionable.

Core Features & Use Cases

  • Systematic task completion: Finds all AITODO markers across the repository, interprets the requested change, and applies updates.
  • Context-aware implementation: Gathers surrounding context for each AITODO line to choose the most consistent implementation approach.
  • Iterative cleanup: Repeats the process until all AITODO comments are gone, reducing stale TODO debt.
  • Use Case: When you receive a set of AITODO notes scattered through multiple files (e.g., missing edge-case handling or incomplete features), use this Skill to implement each requested fix and remove the markers after completion.

Quick Start

Use the aitodo skill to resolve all tasks described in AITODO comments throughout the repository and remove those comments once the changes are implemented.

Frequently Asked Questions about aitodo

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

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

You can resolve inline TODO comments by searching the repository for AITODO markers, deriving required code changes from surrounding context, applying fixes, and removing the markers. This automates feature completion and bug fix follow-ups.

What is the best way to clean up stale TODO debt across multiple files?

Cleaning up stale TODO debt involves iterating through repository-wide AITODO comments, gathering task context per match, planning deterministic code changes, and removing markers once implemented. This reduces scattered technical debt across files.

How does context-aware code maintenance work for inline task instructions?

Context-aware code maintenance works by locating each AITODO marker, gathering surrounding code context to choose the most consistent implementation approach, and applying deterministic changes. This ensures requested refactoring matches existing code patterns.

Can I use this for repository-wide refactoring tasks documented as inline TODOs?

Yes, this handles repository-wide refactoring tasks documented as inline TODOs by executing a repository search for AITODO markers, collecting task context per match, planning deterministic changes, and iterating until no AITODO comments remain.

Do I need any external dependencies to run AITODO task resolution?

No external dependencies are required to run AITODO task resolution. The Skill operates independently to locate markers, derive code changes from context, and apply fixes for documented feature completion or bug fix follow-ups.

Why are my AITODO markers still in the code after running the task resolution?

AITODO markers remain if the iterative cleanup process was interrupted before completion. The Skill repeats the resolution process until no AITODO comments remain, ensuring all requested fixes are implemented and outdated comments are removed.