resolve_todo_parallel

Name: resolve_todo_parallel
Availability: InStock
Author: jimmychen-nxp

Resolve pending TODO comments in markdown files with parallel processing.

1|Updated Mar 11, 2026

Search Tags:#automation #git #documentation #parallel processing #todo #code cleanup

Ready to run

npx skills add https://github.com/JimmyChen-NXP/zephyr-team-activity-dashboard --skill resolve-todo-parallel-jimmychen-nxp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resolve_todo_parallel
Source: https://github.com/JimmyChen-NXP/zephyr-team-activity-dashboard/tree/main/.github/skills/resolve_todo_parallel
Command: npx skills add https://github.com/JimmyChen-NXP/zephyr-team-activity-dashboard --skill resolve-todo-parallel-jimmychen-nxp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of finding and resolving TODO comments within markdown files, streamlining code and documentation cleanup.

Core Features & Use Cases

Automated TODO Finding: Scans specified directories for unresolved TODO comments.
Intelligent Filtering: Skips TODOs related to specific directories (docs/plans/, docs/solutions/) that are marked as wont_fix.
Dependency-Aware Planning: Analyzes TODOs for dependencies and creates a visual plan (Mermaid diagram) for sequential or parallel execution.
Parallel Execution: Spawns independent agents to resolve each TODO concurrently, significantly speeding up the process.
Automated Commit & Push: Commits resolved changes and updates the remote repository.

Quick Start

Use the resolve_todo_parallel skill to find and resolve all pending todos.

Frequently Asked Questions about resolve_todo_parallel

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

FAQPage Schema

How do I automatically resolve pending TODO comments in markdown files?▼

You can automate TODO resolution by scanning markdown files for pending comments, analyzing inter-dependencies, and using parallel agents to resolve them concurrently before committing and pushing the changes to git.

What is dependency-aware planning for parallel code cleanup?▼

Dependency-aware planning analyzes pending TODO comments to identify execution dependencies, generating a visual Mermaid diagram that dictates whether resolution agents should run sequentially or in parallel for optimal code cleanup.

Can I exclude specific directories like docs/plans from automated TODO resolution?▼

Yes, intelligent filtering can skip specific directories such as docs/plans or docs/solutions, automatically excluding TODO comments that are marked as wont_fix from the parallel processing workflow.

How do I commit and push resolved TODO changes automatically to a remote repository?▼

Automated commit and push workflows handle this by taking the resolved TODO changes from the parallel agents, committing them locally, and automatically updating the configured remote git repository.

Does parallel processing work for resolving independent TODO items in documentation?▼

Yes, parallel processing spawns independent agents to concurrently resolve separate TODO items within documentation, significantly accelerating cleanup times compared to sequential execution of independent tasks.

When should I not use parallel agents for TODO resolution?▼

You should avoid parallel agents for TODO resolution when items have strict execution dependencies requiring sequential processing, or when dealing with compound-engineering artifacts that need specific manual exclusions.