daily-register-github-issue-based-on-comments-in-codebase

Creates GitHub issues from TODO, FIX, and REFACTOR comments found in a codebase.

1|Updated Apr 3, 2021
One-click install
npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill daily-register-github-issue-based-on-comments-in-codebase-naoyamiyagawa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-register-github-issue-based-on-comments-in-codebase
Source: https://github.com/NaoyaMiyagawa/dotfiles/tree/main/.claude/scheduled-tasks/daily-register-github-issue-based-on-comments-in-codebase
Command: npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill daily-register-github-issue-based-on-comments-in-codebase-naoyamiyagawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Actionable TODO, FIX, and REFACTOR comments scattered across a codebase are easily forgotten and never tracked. This Skill scans the latest develop branch for such comments and converts them into properly labeled GitHub issues so technical debt becomes visible and manageable. ## Core Features & Use Cases - Comment Scanning: Greps the codebase for TODO, FIX, and REFACTOR comments authored by you after pulling the latest develop branch. - Issue Creation with Prefixes: Creates GitHub issues titled with [TODO], [FIX], or [REFACTOR] prefixes, quoting the original comment and its file location in the description. - Deduplication and Ownership Rules: Skips comments written by others, avoids duplicate issues by updating similar existing ones, and leaves issues unassigned for later triage. - Use Case: Run it as a daily scheduled routine so every new TODO comment you left during yesterday's coding session automatically becomes a tracked GitHub issue the next morning. ## Quick Start Scan the develop branch for my TODO, FIX, and REFACTOR comments and register GitHub issues for any that are not already tracked.

Frequently Asked Questions about daily-register-github-issue-based-on-comments-in-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn TODO comments in code into GitHub issues?

Grep the codebase for TODO, FIX, and REFACTOR comments, then create a GitHub issue for each one using a bracketed prefix like [TODO] in the title. Quote the original comment and its file path and line number in the issue description for context.

How to avoid creating duplicate GitHub issues from code comments?

Before creating a new issue, search existing issues for very similar titles or content. If a matching issue already exists, edit its description to cover the new comment portion instead of opening a duplicate.

Can I filter TODO comments by author before creating issues?

Yes, the workflow only processes comments written by you and skips comments authored by others. This keeps the generated issues scoped to your own action items and avoids filing issues on behalf of teammates.

Should auto-created GitHub issues be assigned automatically?

No, this workflow deliberately leaves new issues unassigned. The author reviews the created issues and self-assigns them later, allowing a separate routine to pick up the work in an orderly triage process.

What branch does the comment scan run against?

The scan runs against the develop branch after performing a git pull to fetch its latest state. This ensures issues reflect the current codebase rather than stale local changes.