
from claude-code-toolkit11
Create or link bug sub-issues: interactively gather context, create a well-structured GitHub bug issue, or add existing issues to a tracking PR.
This skill streamlines creating and managing bug sub-issues on GitHub. It supports three modes: adding existing issues to a tracking PR, creating a new bug issue from a provided title, or launching an interactive flow that gathers context (git logs, branch info, logs) and writes a complete issue body. The skill automates label handling, tracking PR updates, and optional native GitHub sub-issue linking via GraphQL.
Use the skill when you need to convert ad-hoc bug reports into actionable GitHub issues, ensure consistent labeling and tracking, or bulk-link existing bugs into an epic's tracking PR. It's useful during development workflows where issues must be tied to parent epics and tracking tables.
has_scripts is false in the fetch output; the SKILL body documents required CLI calls and files to read.gh, and linking sub-issues via the GitHub GraphQL API.gh and local helper scripts to inspect branches, fetch issues, and update PR bodies.Bug sub-issue creation skill for the claude-code-toolkit ecosystem. Three well-defined modes (add existing, create with title, interactive). No bundled scripts — relies on ~/.claude/bin/ helpers on the host. SKILL.md is thorough with clear step-by-step workflows and good disambiguation logic, but error handling for missing dependencies or failed commands is sparse.
No security concerns — no remote code execution patterns, no credentials, no destructive commands. The skill is well-documented with clear workflows. Main limitation is tight coupling to the claude-code-toolkit ecosystem and its specific ~/.claude/bin/ scripts, which aren't bundled. Usefulness is niche — primarily for teams already using the claude-code-toolkit issue management pattern.