665,000+ skills indexed

DennisTomaCOMMUNITY

Explore all skills by this author →

Verified:GitHub

todo-collector

Scan codebases for TODO, FIXME, HACK, XXX, and BUG markers and generate a prioritized Markdown report.

Updated Aug 23, 2026

Search Tags:#reporting #todo #grep #static-analysis #software-engineering #code-debt

One-click install

npx skills add https://github.com/DennisToma/repo_example --skill todo-collector

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: todo-collector
Source: https://github.com/DennisToma/repo_example/tree/main/.claude/skills/_example-todo-collector
Command: npx skills add https://github.com/DennisToma/repo_example --skill todo-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly surface and prioritize technical debt by extracting in-code markers like TODO, FIXME, HACK, XXX, and BUG across a codebase and generating a structured report.

Core Features & Use Cases

Marker discovery: Scans code files to locate common debt indicators (TODO, FIXME, HACK, XXX, BUG) with file and line references.
Prioritization & categorization: Classifies findings by type and severity to highlight critical areas needing attention.
Generated report: Produces a portable Markdown report suitable for task tracking, code reviews, or roadmap planning.

Quick Start

Use the todo-collector skill to scan the repository for outstanding markers in src/, lib/, app/, and the project root, then review the generated report.

Frequently Asked Questions about todo-collector

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

FAQPage Schema

How do I extract TODO and FIXME comments from code for technical debt reporting?▼

To extract TODO and FIXME comments for technical debt reporting, scan source directories like src/, lib/, and app/ to locate markers and generate a structured Markdown report with file paths and line numbers.

What is the best way to prioritize code debt markers across a project?▼

The best way to prioritize code debt markers is to scan for TODO, FIXME, HACK, XXX, and BUG patterns, then assign priorities by severity to produce a categorized report highlighting critical areas needing attention.

Can I scan specific directories like src and lib for HACK and BUG markers?▼

Yes, you can scan specific directories like src, lib, and app for HACK and BUG markers. The tool operates across common source directories and the project root to extract debt indicators with file and line references.

How do I generate a Markdown report of technical debt from in-code markers?▼

Generate a Markdown report of technical debt by scanning the codebase for in-code markers, categorizing findings by type and severity, and outputting a portable document suitable for task tracking and code reviews.

Does this technical debt scanner require any dependencies to run?▼

No, this technical debt scanner requires no dependencies to run. It operates directly on the codebase to extract marker patterns and metadata without needing external components or setup.

Related Skills

Explore More Software Engineering Skills→

ponytail-debt

Scan source files for ponytail comments and generate a debt ledger.

dex-plan

Convert markdown planning documents into dex tasks with optional subtasks.

code-quality-and-review

Enforce code correctness, readability, and safety with linters and type checkers.

tech-debt

Scan codebases for technical debt and generate prioritized severity reports.