skills.rest
RafayelGardishyan
RafayelGardishyanCOMMUNITY
Explore all skills by this author →
GitHub

file-todos

Create and manage markdown todos from code-review findings.

Updated Mar 9, 2026
Search Tags:#automation#workflow#markdown#dependencies#todo#triage#code-review
One-click install
npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill file-todos-rafayelgardishyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/RafayelGardishyan/rafayels-marketplace/tree/main/plugins/rafayels-engineering/.opencode/skills/file-todos
Command: npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill file-todos-rafayelgardishyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The File-Based Todo Tracking Skill provides a structured workflow for turning scattered feedback, code review notes, and technical debt into persistent, searchable markdown todos stored in the todos/ directory.

Core Features & Use Cases

  • Create todos from findings or feedback and manage their lifecycle (pending -> ready -> complete).
  • Triage, track dependencies, and link related work to PR reviews and code changes.
  • Convert PR comments or code findings into tracked work and log progress over time.

Quick Start

Copy the template to the todos/ directory using the next available ID and fill in 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 findings as markdown todos?▼

Code review findings are tracked as markdown todos by applying a frontmatter-driven template that organizes status, priority, and dependencies into persistent, searchable files within a dedicated todos directory.

What is the best way to manage technical debt and dependencies across pull requests?▼

Managing technical debt across pull requests is best handled by converting scattered feedback into tracked markdown files, enabling you to triage dependencies and link related work directly to code changes.

How do I triage code review notes using a markdown workflow?▼

To triage code review notes using a markdown workflow, you apply a templates-based process that moves items through a pending, ready, and complete lifecycle while tracking dependencies in frontmatter.

Can I convert PR comments into tracked work items without external tools?▼

Yes, you can convert PR comments into tracked work items by copying a structured template into your todos directory, assigning the next available ID, and filling in the required frontmatter sections.

Does this file-based todo tracking approach work for cross-team planning?▼

Yes, file-based todo tracking supports cross-team planning by enforcing a standardized markdown format with frontmatter fields for priority and dependencies, making technical debt visible and searchable across teams.

Related Skills

Explore More Software Engineering Skills→
CristoVenturesCristoVentures
2

file-todos

Create and manage markdown todos with YAML frontmatter in the todos/ directory.

Official
Intermediate
minhcopilotminhcopilot
1

file-todos

Create and manage markdown todos with YAML frontmatter in the todos/ directory.

Community
Basic
cloudvoyantcloudvoyant

pr-fix

Fetch open pull requests and generate proposed code fixes for unresolved review comments.

Official
Intermediate
iliaaliliaal

file-todos

Manage development tasks and technical debt in Markdown files within a 'todos/' directory.

Community
Intermediate