todo-to-skill

Convert project TODO comments into reusable agent skills with SKILL.md frontmatter.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill todo-to-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-to-skill
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/todo-to-skill
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill todo-to-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TODOs in codebases slow teams down by blocking automation opportunities. This skill scans repositories to identify repetitive or missing automation workflows described by TODO comments and converts them into formal, reusable agent skills ready for deployment.

Core Features & Use Cases

  • Todo discovery: scans code for TODO patterns indicating repetitive tasks or automation gaps.
  • Skill extraction: transforms found TODOs into SKILL.md entries with proper frontmatter and step definitions.
  • Codebase uplift: updates skill indexes and suggests immediate automation opportunities across projects.
  • Use Case: A maintainer notices 20 TODOs about deployment automation and uses this skill to generate 5 ready-to-use agent skills, reducing manual boilerplate work.

Quick Start

To begin, run the skill to convert existing TODO comments into automated agent capabilities.

Frequently Asked Questions about todo-to-skill

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

FAQPage Schema
How do I convert TODO comments into automated workflows?

Yes, you can automate repetitive tasks by parsing source code comments to discover TODO patterns that indicate automation gaps, then translating those extracted intents into reusable agent skills aligned with existing skill indexes.

Can I generate agent skills from existing code TODOs across multiple programming languages?

Generating agent skills from code TODOs applies to multi-language repositories, parsing source code comments to identify repetitive tasks and outputting valid SKILL.md files with standardized name and description metadata.

What is the best way to extract actionable intents from code comments for automation?

You can update skill indexes and suggest immediate automation opportunities across projects by aligning newly generated skills with existing indexes, reducing manual boilerplate work for maintainers handling multiple TODO comments.

Does this approach work for multi-language repositories with existing skill indexes?

Yes, this approach works for multi-language repositories by parsing source code comments to extract actionable intents, generating valid SKILL.md frontmatter, and aligning new skills with your existing skill indexes.