convert-github-issues-to-fixmes

This Skill automates converting triaged GitHub issues into inline FIXMEs within code files. It fetches open labeled issues, filters authorized comments, and inserts FIXMEs directly into the relevant codebase locations to ensure direct developer action and traceability.

Automating GitHub issue triage is best handled by converting authorized issue comments into inline FIXMEs. This approach creates a dedicated branch, adds contextual code comments at precise locations, and logs ignored cases to ensure approved tasks are reflected directly in the codebase.

Yes, you need the gh, jq, and git command-line tools installed to process GitHub issues into code comments. These dependencies are required to fetch issues, parse JSON metadata, and manage the dedicated branch where the inline FIXMEs are deployed.

Yes, you can filter GitHub issue comments to only process authorized user feedback. The Skill fetches open issues with specific labels and filters the comments to ensure only approved users' feedback is converted into inline FIXMEs within the codebase.

Branch management when adding FIXMEs from GitHub issues works by creating a dedicated processing branch. This isolates the code comments generated from triaged issues, supporting systematic triage and a clean pull request before merging changes into the main codebase.

GitHub issues that are ignored during the triage conversion process are logged as non-issues. Instead of inserting an inline FIXME in the code, the Skill records these ignored cases to maintain documentation accuracy and provide visibility into why certain issues were bypassed during triage.