Create structured todo Markdown files with YAML frontmatter in .claude/todos.
npx skills add https://github.com/lucasmccomb/ccgm --skill todo-create-lucasmccomb
Please help me install this Agent Skill. Skill: todo-create Source: https://github.com/lucasmccomb/ccgm/tree/main/modules/todos/skills/todo-create Command: npx skills add https://github.com/lucasmccomb/ccgm --skill todo-create-lucasmccomb
Capture small review findings, PR comments, and tech-debt items that are too small for GitHub issues so they are not forgotten, and store them as discoverable, versioned todo files in the repository.
Run /todo-create with a concise description of the finding to write a new .claude/todos/NNN-pending-{priority}-{slug}.md file in the repository.
High-intent search queries and answers about installing and using this skill.
You can capture code review findings and PR comments as structured todo markdown files by writing them into the .claude/todos directory with enforced YAML frontmatter, zero-padded sequence numbers, and inferred priority metadata.
Tracking small tech-debt items is best handled by creating lightweight todo markdown files directly in the repository, ensuring observations are versioned and discoverable rather than lost in ad-hoc notes or forgotten review nits.
To automate todo creation from a triage workflow, you can programmatically invoke a canonical writer that infers priority, source, PR number, and touched files from structured input, returning the created file path for downstream processing.
Yes, the todo markdown schema enforces filename conventions such as NNN-pending-{priority}-{slug}.md and requires YAML frontmatter to maintain consistency across todos created for code review and planning notes.
You can save debug findings and planning follow-ups as structured markdown todos inside your repository's .claude/todos directory, providing a lightweight alternative to full GitHub issues for off-path observations.
You should avoid using structured markdown files for repository todos when items require extensive discussion threads, cross-references, or external visibility, as these lightweight files lack the collaborative tracking features of dedicated issue trackers.
marcusrbrownManage file-based todos as markdown files with YAML frontmatter.
jikig-aiConvert legacy markdown todos into actionable entries with YAML frontmatter updates.
justsmlCoordinate parallel code review specialists to produce a unified PR verdict.
jguadagnoScan GitHub issues and discussions, draft responses, and route them for human review.
