Claude Skill

todo-extractor

Finds TODO, FIXME, HACK and XXX comments across a source tree and groups them by tag and file. Use when the user asks for a list of open tasks in the code, wants to plan cleanup work, or needs an inventory of technical debt.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies

#planning

Download lethe044-agentskill-kit-skills_todo-extractor-219c6e5.zip · 2 KB

Install

skills CLI npx skills add https://github.com/Lethe044/agentskill-kit/tree/main/skills/todo-extractor
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install lethe044-agentskill-kit@llmmart
Git git clone https://github.com/Lethe044/agentskill-kit.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole lethe044/agentskill-kit collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

TODO extractor

Turns scattered comments into a planning list.

When to use

  • The user asks "what is left to do in this repo?".
  • Planning a cleanup sprint or a release, where known shortcuts must be reviewed.
  • Before archiving or handing over a project.

How to run

python scripts/find_todos.py src/
python scripts/find_todos.py . --tags TODO,FIXME

Hidden folders, node_modules, venv, dist, build and binary files are skipped.

Output

JSON with total, by_tag (counts) and items, a list of {"file", "line", "tag", "text"} sorted by file and line. The exit code is always 0 when the path exists.

After running

  1. Lead with the counts per tag. FIXME and HACK usually matter more than TODO.
  2. Group items by file or folder and point out hot spots.
  3. Propose an order of work, and mark items that look stale (they mention past dates or removed code).

Errors

A path that does not exist exits with code 2.

Files (agentskill-kit)
  • scripts
    • find_todos.py 2.2 KB
      Loading…
  • tests
    • cases.json 1.4 KB
      Loading…
  • SKILL.md 1.3 KB
    ---
    name: todo-extractor
    description: Finds TODO, FIXME, HACK and XXX comments across a source tree and groups them by tag and file. Use when the user asks for a list of open tasks in the code, wants to plan cleanup work, or needs an inventory of technical debt.
    license: MIT
    metadata:
      version: 1.0.0
      author: Lethe044
      tags: [todo, technical-debt, code-search, planning]
    ---
    
    # TODO extractor
    
    Turns scattered comments into a planning list.
    
    ## When to use
    
    - The user asks "what is left to do in this repo?".
    - Planning a cleanup sprint or a release, where known shortcuts must be reviewed.
    - Before archiving or handing over a project.
    
    ## How to run
    
    ```bash
    python scripts/find_todos.py src/
    python scripts/find_todos.py . --tags TODO,FIXME
    ```
    
    Hidden folders, `node_modules`, `venv`, `dist`, `build` and binary files are skipped.
    
    ## Output
    
    JSON with `total`, `by_tag` (counts) and `items`, a list of `{"file", "line", "tag", "text"}`
    sorted by file and line. The exit code is always 0 when the path exists.
    
    ## After running
    
    1. Lead with the counts per tag. `FIXME` and `HACK` usually matter more than `TODO`.
    2. Group items by file or folder and point out hot spots.
    3. Propose an order of work, and mark items that look stale (they mention past dates or removed code).
    
    ## Errors
    
    A path that does not exist exits with code 2.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.