file-todos

Manage file-based todos for code review and task tracking.

1|Updated Jan 11, 2025
One-click install
npx skills add https://github.com/krbylit/dotfiles --skill file-todos-krbylit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/krbylit/dotfiles/tree/main/cm-util/pkg-backups/beads-compound/0.6.8/gemini/skills/file-todos
Command: npx skills add https://github.com/krbylit/dotfiles --skill file-todos-krbylit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Create new todos from findings or feedback using a consistent file template.
  • Manage todo lifecycle (pending → ready → complete) and track dependencies between items.
  • Triages pending items to decide on priority and recommended actions, aligning with code review processes.

Quick Start

Create a new todo by copying the template from assets/todo-template.md into todos/ and filling the required sections.

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 in markdown files?

Code review todos can be tracked in markdown files by applying structured templates with YAML frontmatter metadata. This approach automates creation, triage, and lifecycle management from pending to complete states.

What is the best way to manage todo dependencies during code review?

Managing todo dependencies during code review involves tracking relationships between pending items and their prerequisite tasks. Structured markdown templates with YAML frontmatter enable consistent dependency logging across multiple revisions and pull requests.

Can I use slash commands to automate todo triage workflows?

Slash command integrations can automate todo triage workflows by driving consistent lifecycle transitions from pending to ready to complete. This aligns task prioritization directly with ongoing code review processes.

How do I create consistent todo files for development workflows?

Consistent todo files for development workflows are created by copying a markdown template into a designated todos directory. The template enforces required YAML frontmatter metadata and structured sections for uniform task tracking.

Does file-based todo tracking require any external dependencies?

File-based todo tracking requires no external dependencies. It operates entirely on structured markdown templates and YAML frontmatter stored locally in a todos directory, making it lightweight and portable.

When should I use a file-based todo system over other tracking approaches?

A file-based todo system is ideal when your code review process demands structured markdown templates, dependency tracking across multiple revisions, and slash-command integrations within the development workflow repository itself.