From devstefancho-skills
Fetches, creates, or updates GitHub issues using the gh CLI. Handles attachment downloads and video frame extraction. Activate when the user mentions GitHub issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devstefancho-skills:github-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Operate on GitHub issues with the `gh` CLI. One skill, three operations — dispatch on the user's words or the argument:
Operate on GitHub issues with the gh CLI. One skill, three operations — dispatch on the user's words or the argument:
| User intent | Operation |
|---|---|
"이슈 N 가져와 / 조회 / 작업", "fetch issue N", bare /github-issue 94 | Fetch |
| "이슈 등록 / 생성 / 만들어줘", "create issue", "file a bug" | Create |
| "이슈 N 수정 / 업데이트 / 코멘트 / 닫아줘", "update issue N" | Update |
If the intent is genuinely ambiguous, ask which operation — don't guess.
gh auth status works once; if not, stop and tell the user to run gh auth login.-R <owner>/<repo> to every gh call.gh issue list, show the open issues, and let the user pick.gh issue view <N> --json number,title,state,labels,author,url,body,commentsPick a template, in this order:
.github/ISSUE_TEMPLATE/*.md|*.yml if present — list them and match by intent.Fill the template from the conversation and any context the user gave. Write the issue in the language of the repo's existing issues (check a recent one if unsure). Ask only for fields you genuinely can't fill — don't interrogate.
Show the complete draft (title, body, labels) and wait for the user's OK before creating. Filing an issue is outward-facing and visible to others; never skip this gate.
Create with a body file so markdown survives quoting:
gh issue create --title "<title>" --body-file <draft.md> --label "<labels>"
Only pass labels that already exist in the repo (gh label list) — gh errors on unknown labels. Same rule for --add-label on update.
Report the created issue URL.
gh issue view <N> --json title,body,labels,state) — never edit blind.gh issue edit <N> --title/--body-file/--add-label/--remove-labelgh issue comment <N> --body-file <comment.md>gh issue close <N> [--comment] / gh issue reopen <N>curl <attachment-url> or WebFetch on github.com/user-attachments/assets/... → 404. RIGHT: download with Authorization: token $(gh auth token) per fetching.md..mp4 directly (wastes a turn, shows nothing). RIGHT: extract frames with ffmpeg and Read those.gh issue create/edit straight away with a body you never showed. RIGHT: full draft → user confirmation → apply.npx claudepluginhub devstefancho/skillsCreates well-structured GitHub issues using gh CLI with templates for bugs, features, tasks including titles, descriptions, acceptance criteria, and labels. Use for filing bugs or feature requests.
Creates, lists, and views GitHub issues using gh CLI with guided prompts for actions, titles, bodies, and issue types. For repository issue management workflows.
Resolves GitHub issues via 8-phase workflow: fetch details, analyze requirements, implement solutions, verify correctness, code review, commit changes, create PRs. Activates on resolve, implement, fix requests or issue references.