file-todos

Name: file-todos
Availability: InStock
Author: jayteealao

Track code review feedback and work items in .claude/todos with YAML frontmatter.

Updated Jan 1, 2026

Search Tags:#templates #markdown #todo #triage #code-review #worklog #dependency

Ready to run

npx skills add https://github.com/jayteealao/blank-template --skill file-todos-jayteealao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/jayteealao/blank-template/tree/main/.claude/skills/file-todos
Command: npx skills add https://github.com/jayteealao/blank-template --skill file-todos-jayteealao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill helps teams manage a file-based todo tracking system in the .claude/todos/ directory, enabling structured creation, status transitions, dependency tracking, triage workflows, and integration with slash commands and code review processes.

Core Features & Use Cases

File-based todos for capturing code review feedback, technical debt, feature requests, and work items.
Lifecycle management from pending to ready to complete, including dependency handling and triage.
Integration with slash commands and code-review workflows to streamline collaboration and tracking.

Quick Start

Copy the provided template and create your first todo: cp assets/todo-template.md .claude/todos/001-pending-p2-example-todo.md Then edit the sections: Problem Statement, Findings, Proposed Solutions, Acceptance Criteria, and Work Log as you triage and execute work.

Frequently Asked Questions about file-todos

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

FAQPage Schema

How do I track code review todos using markdown files?▼

Code review todos are tracked by creating markdown files in a local .claude/todos directory, using YAML frontmatter for metadata and structured sections for problem statements, findings, and proposed solutions to maintain consistent formatting.

What is the best way to triage technical debt from PR reviews?▼

Triage technical debt from PR reviews by applying a file-based workflow that transitions items from pending to ready to complete, capturing feedback in markdown templates with dependency tracking and work logs.

How do I manage dependencies between code review work items?▼

Dependency management between code review work items is handled through YAML frontmatter metadata in local markdown files, allowing you to link and track related todos across the .claude/todos directory during triage.

Can I use slash commands to integrate file-based todos with code review workflows?▼

Yes, file-based todos integrate with slash commands and code review workflows, enabling teams to streamline collaboration by triggering creation, status transitions, and triage directly within the review process.

What sections should a code review todo markdown template include?▼

A code review todo markdown template should include Problem Statement, Findings, Proposed Solutions, Acceptance Criteria, and Work Log sections, guided by an assets-based template for consistent formatting.

Does file-based todo tracking require external dependencies?▼

No, file-based todo tracking requires no external dependencies, relying solely on a local .claude/todos directory with markdown files and YAML frontmatter to manage the full todo lifecycle.