issue-update
Updates an existing GitHub issue: edits the body, posts a comment, retags, or reopens, acknowledging stale framing instead of silently rewriting it, and previews before applying. Use when the user asks to update, comment on, relabel, or reopen an issue, or when a workflow needs to post a progress checkpoint to a tracking issue.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- issue-update
- description
- Updates an existing GitHub issue: edits the body, posts a comment, retags, or reopens, acknowledging stale framing instead of silently rewriting it, and previews before applying. Use when the user asks to update, comment on, relabel, or reopen an issue, or when a workflow needs to post a progress checkpoint to a tracking issue.
- allowed-tools
- Bash(gh issue *), Bash(gh api *), Bash(gh label list*), Read
- argument-hint
- <#> | reopen <#>
03 SKILL.md 正文
Issue Update
Keep an issue accurate as understanding changes, without erasing the history that produced it. A reader arriving cold should see the current truth; a reader following the thread should see how it got there.
<#> updates an open issue; reopen <#> reopens a closed one with new
context.
1. Read the whole thread
gh issue view <#> --json title,body,state,labels,comments
The comments often hold the latest framing, so the body alone can mislead.
Note alternative approaches, corrections, file:line samples, cross-links,
and labels added after filing. --json comments returns at most the first
100; for a longer thread, fetch them all so a late change of framing isn't
missed:
gh api --paginate "repos/<owner>/<repo>/issues/<#>/comments"
Done when you've read every comment, and can say what the thread currently believes.
2. Update an open issue
Pick the change:
| Situation | Action |
|---|---|
| The original framing is wrong | Edit the body and comment acknowledging the change |
| New information builds on the framing | Comment only |
| The body is wrong but its history should stay visible | Edit the body under a "Note:" header; the comment links to the old framing |
| Scope or priority shifted, the text is fine | Labels only |
When you correct framing, say what was wrong rather than rewriting silently. Open the new body with a note, so cold readers know it's current, thread readers see what shifted and why, and nobody re-litigates the original:
> **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>
Check labels against gh label list. For a label that doesn't exist, skip it
and suggest it in the comment ("Suggest adding an area:foo label; it
doesn't exist yet"). Leave gh label create to the maintainer, because the
label set is a repo-config decision.
If the thread surfaced related issues or PRs that don't link back, draft a one-line cross-link comment for each of them too.
Show the user the drafted body, the comment, the label diff, and any cross-link comments, and wait for confirmation: an edit can overwrite framing. Then run only the commands that apply:
gh issue edit <#> --body "$(cat <<'EOF'
<new body>
EOF
)"
gh issue comment <#> --body "..."
gh issue edit <#> --add-label "..." --remove-label "..."
gh issue comment <related#> --body "Related: #<#> ..." # per cross-link
Done when the confirmed changes are applied and every newly found related issue or PR links both ways.
3. Reopen a closed issue
-
Confirm why it closed, from the thread: the resolution comment, a label, or the linked PR.
-
If a merged PR closed it but the problem persists (a regression, a partial fix, scope found after merge), read that PR's diff and comments to confirm what it actually shipped. When the gap has a different root cause, a fresh issue that links back is usually cleaner than a reopen: call the Skill tool with "issue-create" instead and stop here.
-
Draft a comment saying what changed and why the close was premature or no longer applies. After a merged PR, name the gap precisely: "PR #X shipped Y, but Z still reproduces because …".
-
Show the user the comment, and wait for confirmation. Reopen with the comment attached, so the reopen is never silent:
gh issue reopen <#> --comment "..." -
If the scope shifted, preview the label diff and apply it.
Done when the issue is open with a comment explaining why, and its labels match its scope.
Related
issue-create— file a new issue.issue-close— close as resolved, superseded, or duplicate.issue-restructure— split or merge issues.
04 同仓库更多 Skills
teach
Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.
svg-logo-designer
Generate SVG logos with multiple concepts, layouts, and color variations.
documentation-writer
Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use /skill-writer instead.
adhd-mode
Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says "stop adhd mode". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.
wait-what
That last message didn't land: re-explain it with the missing context.
to-questionnaire
Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.