file-todos

Create file-based Markdown todos with YAML frontmatter for code review work items.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/The-Rabak/naysmith --skill file-todos-the-rabak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/file-todos
Command: npx skills add https://github.com/The-Rabak/naysmith --skill file-todos-the-rabak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The File-Based Todo Tracking Skill provides a standardized, file-based approach to tracking code review findings and related work items as Markdown files, ensuring consistent documentation and easy sharing.

Core Features & Use Cases

  • Create new todos from findings or feedback using a standardized template.
  • Track lifecycle (pending → ready → complete), priorities, and dependencies to support triage and planning.
  • Maintain comprehensive work logs and notes for accountability and future reference.
  • Integrate with slash commands and code review workflows to streamline collaboration.

Quick Start

Copy the template to the todos directory and start a new todo with a unique ID.

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 findings as markdown todos in my repository?

You can track code review findings as markdown todos by applying a standardized template with YAML frontmatter to each file. This enforces consistent documentation, structured sections, and reliable parsing across your repository.

How do I organize code triage and work logs for development tasks?

Organize code triage by tracking task lifecycle from pending to complete, setting priorities, and documenting dependencies. This approach maintains comprehensive work logs and structured notes for accountability and future reference.

What is the best way to standardize markdown files for auditing code issues?

Standardizing markdown files for auditing requires enforcing a consistent YAML frontmatter and structured sections in each todo. This ensures reliable parsing, easy sharing, and uniform documentation of code issues.

Can I integrate file-based todos with code review workflows?

Yes, you can integrate file-based todos with code review workflows by using slash commands. This streamlines collaboration by automatically creating new todos from findings or feedback using the standardized template.

Do I need any dependencies to use a file-based todo system?

No dependencies are required to use the file-based todo system. You simply copy the provided template to your todos directory and start a new todo with a unique ID to begin tracking work items.

When should I use markdown files instead of a database for issue tracking?

Use markdown files for issue tracking when you need a standardized, file-based approach that ensures consistent documentation and easy sharing directly within your repository, avoiding external database management overhead.