resolve-todo-parallel

Analyze dependencies in markdown TODO files and spawn parallel pr-comment-resolver agents.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill resolve-todo-parallel-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-todo-parallel
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/resolve-todo-parallel
Command: npx skills add https://github.com/jikig-ai/soleur --skill resolve-todo-parallel-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the resolution of legacy local CLI TODO markdown files found in the todos/ directory, eliminating manual triage and ensuring dependent changes are executed in the correct order to avoid breaking work flows.

Core Features & Use Cases

  • Bulk TODO discovery: Scans todos/*.md for unresolved items and produces a structured list grouped by type.
  • Dependency analysis & planning: Analyzes inter-item dependencies, prioritizes blocking tasks, and emits a mermaid flow diagram to guide execution order.
  • Parallel resolution: Spawns a pr-comment-resolver agent for each unresolved item to apply fixes in parallel, then commits, removes the TODO, and pushes changes.
  • Use Case: Ideal for repositories with legacy local TODO files that predate GitHub issue integration and need deterministic, concurrent resolution.

Quick Start

Resolve all pending todos in the todos directory in parallel, analyze dependencies, spawn pr-comment-resolver agents to apply fixes, commit the changes, and push to remote.

Frequently Asked Questions about resolve-todo-parallel

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

FAQPage Schema
How do I resolve local markdown TODO files in parallel?

You can resolve local markdown TODO files in parallel by scanning the todos directory, analyzing dependencies, and spawning pr-comment-resolver agents to apply fixes, commit, and push changes concurrently.

How does dependency analysis work for concurrent task remediation?

Dependency analysis for concurrent task remediation evaluates inter-item dependencies within your TODO files, prioritizes blocking tasks, and renders a mermaid flow diagram to determine the correct parallel execution order.

Can I use this for legacy local todo files that predate GitHub issue integration?

Yes, this is specifically designed for legacy local todo files that predate GitHub issue integration, applying dependency-aware parallel remediation to unresolved markdown files stored in the todos directory.

What is the best way to automate git commits and pushes after resolving todos?

Automating git commits and pushes after resolving todos is handled by spawning a pr-comment-resolver agent per item, which applies the fix, removes the resolved TODO file, and pushes the results to the remote repository.

When should I not use parallel processing for local TODO resolution?

You should avoid parallel processing for local TODO resolution when your markdown files lack clear inter-item dependencies or when sequential execution is required to prevent breaking existing work flows.