메뉴
Update an existing GitHub issue — edit body, post a comment, retag, or reopen. Pre-flights body + comments; acknowledges stale framing instead of silently rewriting.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Close a GitHub issue with discipline — resolved, superseded, or duplicate. Pre-flights body + comments, migrates substance before destroying context, cross-links both directions.
File a new GitHub issue with duplicate search, scope decision, label discovery, and preview before posting. Prevents fragmented or silently-filed issues.
Restructure the topology of GitHub issues — split one into many focused replacements, or merge multiple into one keeper. Migrates substance and cross-links before closing anything.
Review and address PR feedback using 6-dimensional code review
Structured code review using 6 dimensions. Works with or without the code-reviewer agent.
Create conventional commits with quality gates and validation
| name | issue-update |
| description | Update an existing GitHub issue — edit body, post a comment, retag, or reopen. Pre-flights body + comments; acknowledges stale framing instead of silently rewriting. |
| argument-hint | <#> | reopen <#> |
| allowed-tools | Bash(gh issue *), Bash(gh api *), Bash(gh label *), Bash(gh repo *), Read, Edit, Write |
Modify an open issue in place (body / comment / labels) or reopen a closed one with new context — without silently rewriting the original framing.
Keep issues accurate as understanding evolves, without erasing the history that produced the current state.
gh issue view --json comments returns the first 100 comments; paginate via gh api for longer threads (see pre-flight note).gh issue edit, gh issue comment, or gh issue reopen.gh CLI authenticated; issue accessible.gh label list.gh issue view <#> --json title,body,state,labels,comments
Read comments, not just body. Note alternative approaches, corrections, file:line samples, cross-links, late labels.
Note:
gh issue view --json commentsreturns at most the first 100 comments. Sample/paginate viagh api /repos/<owner>/<repo>/issues/<#>/comments?per_page=100&page=N(orgh api --paginate) before editing when the thread is long — otherwise late framing changes can be missed.
| Arg form | Mode |
|---|---|
<#> | update an open issue (body / comment / labels) |
reopen <#> | reopen a closed issue with new context |
Decide: edit body / post comment / both / labels-only. See DETAIL: Choosing Edit vs Comment.
Preview: show the drafted new body, comment text, and label diff to the user. Wait for explicit confirmation before applying — edits can overwrite framing. Then run only the applicable command(s):
gh issue edit <#> --body "$(cat <<'EOF'
> **Note:** Original framing assumed X. Corrected after #123.
## What
<corrected body>
EOF
)"
gh issue comment <#> --body "..."
gh issue edit <#> --add-label "..." --remove-label "..."
Cross-link any newly discovered related issues / PRs.
Confirm closure reason from the pre-flight (resolution comment, label, linked PR).
Compose a comment with new context: what changed, why the original close was premature or no longer applies.
Preview the drafted reopen comment to the user. Wait for confirmation. Then reopen with the comment attached:
gh issue reopen <#> --comment "..."
Update labels if scope shifted (preview the label diff first).
| Situation | Action |
|---|---|
| Original framing is wrong | Edit body and comment acknowledging the change |
| New info builds on existing framing | Comment only |
| Body is wrong, history should stay visible | Edit body with "Note:" header; comment links to old framing |
| Scope / priority shifted, text fine | Labels only |
The principle: readers arriving cold should see current truth; readers tracking history should see how we got here.
When editing a body to correct framing, preserve the correction trail:
> **Note:** Original framing assumed all suppliers had a stable `code` field.
> Corrected after #123 — the field is nullable for legacy imports. Rewritten
> below.
## What
<corrected body>
This:
If the closing PR shipped but the issue persists (regression, partial fix, scope creep discovered post-merge):
reopen or a fresh issue (/issue-create) that links back. Fresh issue is usually cleaner if the gap has a different root cause.If you want to add a label that doesn't exist:
area:foo label — doesn't exist yet."gh label create from this skill; that's a repo-config decision./issue-create — File a new issue./issue-close — Close as resolved / superseded / duplicate./issue-restructure — Split / merge issues.