file-todos

Track code-review todos without a database by translating findings into structured markdown notes with YAML frontmatter. This file-based tracker organizes technical debt and feature work inside a repository using a consistent template and naming conventions for full portability.

Manage technical debt and feature work using markdown files by applying a structured todo-template with YAML frontmatter. This approach keeps items self-contained, supports status tracking like pending or complete, and ensures reproducible workflows directly within your repository.

Triage pending code review items by organizing file-based todos through a defined lifecycle. You can update status fields from pending to ready or complete, manage dependencies, and link pull request findings to actionable tasks using slash commands.

Yes, you can integrate file-based todo tracking with your code review process. The workflow supports linking pull request findings to actionable tasks and uses slash commands to triage and manage dependencies within your standard review lifecycle.

No, this file-based todo tracker requires no external dependencies. It operates entirely within a single repository using structured markdown files, YAML frontmatter schemas, and optional blocks for dependencies, assets, and references to maintain discoverability.

Use a markdown todo template instead of a dedicated issue tracker when you need to manage code-review feedback and technical debt without a database. It provides a lightweight, portable solution that keeps todos self-contained and integrated with your repository workflows.