skills.rest
beratcelik1
beratcelik1COMMUNITY
Explore all skills by this author →
Website𝕏@beratcelik0GitHub

file-todos

Create and manage file-based todos with YAML frontmatter for code review workflows.

1|Updated Mar 5, 2026
Search Tags:#workflow#triage#code-review#worklog#todo-management#issue-dependency#markdown-todos
One-click install
npx skills add https://github.com/beratcelik1/compound-claude --skill file-todos-beratcelik1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/beratcelik1/compound-claude/tree/main/skills/file-todos
Command: npx skills add https://github.com/beratcelik1/compound-claude --skill file-todos-beratcelik1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured file-based todo system for managing code review feedback, technical debt, feature requests, and work items within the todos/ directory, ensuring triage, dependencies, and workflow coordination.

Core Features & Use Cases

  • Create new todos with a standardized file name {issue_id}-{status}-{priority}-{description}.md and frontmatter including status, priority, issue_id, and dependencies.
  • Triage and manage states from pending to ready to complete, with a clear work log and acceptance criteria.
  • Integrate with code review processes by aligning with the review gate and planning steps to ensure work is tracked and learned.

Quick Start

Create a new todo file under todos/ using the next available id and fill in the required frontmatter and 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 feedback and technical debt using markdown files?▼

Structured file-based todo tracking organizes code review feedback by enforcing a YAML frontmatter schema with status, priority, issue_id, and dependencies alongside required sections like Problem Statement and Acceptance Criteria within a dedicated todos/ directory.

What is the best way to manage issue dependencies and triage status for software projects?▼

Managing issue dependencies and triage status is handled by applying a structured markdown workflow that transitions states from pending to ready to complete, using a standardized file naming convention and a clear work log for tracking.

How do I create a new todo file that aligns with a code review workflow?▼

Create a new todo file under the todos/ directory using the next available issue_id. Name it using the {issue_id}-{status}-{priority}-{description}.md convention and populate the required YAML frontmatter and structured markdown sections.

Does a file-based todo system require specific sections for technical debt tracking?▼

Yes, file-based todo tracking requires structured sections including Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, and Work Log to properly document technical debt and coordinate with code review processes.

Can I integrate markdown todos directly with my code review gates and planning steps?▼

Yes, markdown todos integrate with code review processes by aligning with the review gate and planning steps, ensuring work items are actively tracked, triaged, and learned from during the software development lifecycle.

Related Skills

Explore More Software Engineering Skills→
i3ringiti3ringit
3

file-todos

Manage Markdown todo files with YAML frontmatter in the todos/ directory.

Community
Basic
danfrdndanfrdn

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Community
Advanced
kys0213kys0213

git

Automate Git branch creation, TODO-based commits, and PR generation.

Community
Intermediate
zeketxzeketx

file-todos

Manage file-based todos with YAML frontmatter and Markdown files.

Community
Intermediate