todo-review

Verify todo implementation status by inspecting repository files and git history.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/dokdo2013/claude-code-skills --skill todo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-review
Source: https://github.com/dokdo2013/claude-code-skills/tree/main/plugins/todo-review/skills/todo-review
Command: npx skills add https://github.com/dokdo2013/claude-code-skills --skill todo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly determine whether todo items recorded in project memory have been implemented, are in progress, or have not been started, removing guesswork and preventing stale tasks from lingering in the backlog.

Core Features & Use Cases

  • Memory-driven inspection: Loads MEMORY-TODO sections and referenced project-*.md entries to build an investigation list.
  • Parallel read-only sub-agents: Launches up to 7-8 concurrent explorers to check file existence, recent commits, and uncommitted changes for each task.
  • Aggregated recommendations: Classifies items as completed / in-progress / not-started, provides evidence for each classification, and offers a confirmation-driven cleanup flow to remove completed todos.
  • Safeguards: Operates in read-only mode, avoids code modifications, groups items by repository to limit agent churn, and asks for user confirmation before deleting todos.

Quick Start

Ask the assistant to "Review today and yesterday's MEMORY-TODO items, inspect each referenced project file and git history, and return a summarized table of completed, in-progress, and not-started items with recommendations."

Frequently Asked Questions about todo-review

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

FAQPage Schema
How do I verify the implementation status of MEMORY-TODO items across multiple git repositories?

To check todo implementation status, the system reads project memory entries and dispatches up to 7-8 concurrent read-only sub-agents to inspect file existence, recent commits, and uncommitted changes across multiple repositories.

What is the best way to track in-progress and not-started code review tasks in project memory?

Tracking in-progress code review tasks involves running git status and git log checks against referenced project files, aggregating evidence of recent modifications and uncommitted changes to classify task states accurately.

Can I use parallel sub-agents to inspect repository files without modifying code?

Yes, you can use parallel read-only sub-agents to inspect repository files safely. The system operates strictly in read-only mode, avoiding code modifications and grouping items by repository to prevent unnecessary agent churn.

How do I clean up completed MEMORY-TODO items from my project backlog?

To clean up completed MEMORY-TODO items, the system provides an aggregated recommendation table classifying task states and offers a confirmation-driven flow that asks for user approval before removing completed todos from the project memory.

Does task-review work with git commit history to determine if a todo item is completed?

Yes, task-review works with git commit history by running git log to check for recent commits linked to referenced project files, using that commit evidence alongside file existence checks to determine completed or in-progress states.