repotodo

Scan and prioritize code TODO comments by P1/P2/P3/low across a repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams automatically discover, categorize, and track remediation work for codebase TODO comments, reducing drift and accelerating delivery.

Core Features & Use Cases

  • Discover and categorize TODO comments by priority (P1, P2, P3, low) across the repository.
  • Process TODOs with verification, fixes, and optional VERIFY+FIX workflows, generating audit-ready reports.
  • Align findings with source TODOs, and optionally inject missing TODOs to close gaps.

Quick Start

Invoke /repotodo to start scanning the repository for prioritized TODOs and manage remediation.

Frequently Asked Questions about repotodo

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

FAQPage Schema
How do I scan code TODO comments and categorize them by priority across a repository?

Scanning code TODO comments and categorizing them by priority across a repository is automated by extracting and sorting P1, P2, P3, and low priority items. It processes large codebases with multi-file paths to generate actionable remediation reports.

What is the best way to manage code TODO remediation workflows with verification and fixes?

Managing code TODO remediation workflows with verification and fixes is handled through a phase-based process featuring per-item locking, processing, and optional VERIFY+FIX workflows. This ensures drift reduction and produces audit-ready reports.

Can I automatically inject missing TODO comments into source code files?

Automatically injecting missing TODO comments into source code files is supported as an optional feature during the processing phase. This aligns findings with source TODOs to close tracking gaps across the repository.

How does static analysis handle large codebases with multi-file paths during TODO tracking?

Static analysis handles large codebases with multi-file paths during TODO tracking by implementing a phase-based workflow with scanning, per-item locking, and cleanup. This ensures accurate discovery and verification of prioritized remediation items.

Does repotodo require any dependencies to scan and prioritize repository TODO comments?

Repotodo requires no external dependencies to scan and prioritize repository TODO comments. It independently discovers, lists, and verifies P1, P2, P3, and low priority items across your codebase.

Why should I use an automated TODO scanner instead of manually tracking code remediation?

Using an automated TODO scanner instead of manually tracking code remediation reduces drift and accelerates delivery. It categorizes priority items and generates actionable reports, replacing manual static-analysis code-review checks.