resolve-todos

Resolve file-based TODOs through a verify-before-fix pipeline with batch processing.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune --skill resolve-todos-vinhnxv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-todos
Source: https://github.com/vinhnxv/rune/tree/main/plugins/rune/skills/resolve-todos
Command: npx skills add https://github.com/vinhnxv/rune --skill resolve-todos-vinhnxv

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Resolve file-based TODOs using Agent Teams with a verify-before-fix pipeline, preventing hallucinated or unsafe fixes by introducing a verification phase before any changes are applied.

Core Features & Use Cases

  • Parallel discovery, triage, and context gathering across multiple files with ownership enforcement.
  • Verification-before-fix workflow with verifiers and fixers, plus a consolidated quality gate and reporting.
  • End-to-end lifecycle including phase-based orchestration and change-visibility through summary reports.

Quick Start

Invoke /rune:resolve-todos to discover pending TODOs and process them through verification, batch fixing, and a final quality report.

Frequently Asked Questions about resolve-todos

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

FAQPage Schema
How do I verify file-based TODOs before applying automated code fixes?

You can verify file-based TODOs before fixing by using a verify-before-fix pipeline that introduces a verification phase prior to changes, preventing unsafe fixes through parallel agent teams.

What is the best way to batch process TODO resolution across multiple code files?

Batch processing TODO resolution works by running parallel discovery, triage, and context gathering across files with ownership enforcement, followed by verification, fixing, and quality checks.

How does a verify-before-fix pipeline prevent hallucinated code changes?

A verify-before-fix pipeline prevents hallucinated code changes by requiring verifiers to check TODO context before fixers apply changes, concluding with a consolidated quality gate and summary report.

Can I enforce ownership and track state during automated TODO resolution?

Yes, automated TODO resolution supports ownership enforcement across parallel agents and maintains durable state management throughout the discovery, triage, verification, and fixing phases.

What are the limitations of using agent teams for TODO resolution?

Limitations include dependency on structured file-based TODOs and the requirement for sanitized prompts and specific SEC-RESOLVE-001 hooks to ensure safe batch processing and accurate verdict taxonomy reporting.