[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KWW79KHT8PNSBFTY4H9QB0":3,"skill-same:01M6KWW79KHT8PNSBFTY4H9QB0":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6KWW79KHT8PNSBFTY4H9QB0","issue-update",null,"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.","dougborg\u002Fharness-kit","dougborg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1261222?v=4","01M6KWS4PB51EYD4ZDJJSGNGB2","Doug Borg","01M6KWS4T8ZZW6SX5QZS9B5BN2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fissue-update\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"update","issue","issue update","use","Existing","updates","posts","post","progress","stale","github issue","github","list","read","gh","Bash","checkpoint","api","gh issue","workflow","2026-11-10 10:12:30",false,"---\nname: issue-update\ndescription: >-\n  Updates an existing GitHub issue: edits the body, posts a comment, retags,\n  or reopens, acknowledging stale framing instead of silently rewriting it, and\n  previews before applying. Use when the user asks to update, comment on,\n  relabel, or reopen an issue, or when a workflow needs to post a progress\n  checkpoint to a tracking issue.\nargument-hint: \"\u003C#> | reopen \u003C#>\"\nallowed-tools: Bash(gh issue *), Bash(gh api *), Bash(gh label list*), Read\n---\n\n# Issue Update\n\nKeep an issue accurate as understanding changes, without erasing the history\nthat produced it. A reader arriving cold should see the current truth; a\nreader following the thread should see how it got there.\n\n`\u003C#>` updates an open issue; `reopen \u003C#>` reopens a closed one with new\ncontext.\n\n## 1. Read the whole thread\n\n```bash\ngh issue view \u003C#> --json title,body,state,labels,comments\n```\n\nThe comments often hold the latest framing, so the body alone can mislead.\nNote alternative approaches, corrections, `file:line` samples, cross-links,\nand labels added after filing. `--json comments` returns at most the first\n100; for a longer thread, fetch them all so a late change of framing isn't\nmissed:\n\n```bash\ngh api --paginate \"repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fissues\u002F\u003C#>\u002Fcomments\"\n```\n\nDone when you've read every comment, and can say what the thread currently\nbelieves.\n\n## 2. Update an open issue\n\nPick the change:\n\n| Situation | Action |\n| --- | --- |\n| The original framing is wrong | Edit the body **and** comment acknowledging the change |\n| New information builds on the framing | Comment only |\n| The body is wrong but its history should stay visible | Edit the body under a \"Note:\" header; the comment links to the old framing |\n| Scope or priority shifted, the text is fine | Labels only |\n\nWhen you correct framing, say what was wrong rather than rewriting silently.\nOpen the new body with a note, so cold readers know it's current, thread\nreaders see what shifted and why, and nobody re-litigates the original:\n\n```markdown\n> **Note:** Original framing assumed all suppliers had a stable `code` field.\n> Corrected after #123: the field is nullable for legacy imports. Rewritten\n> below.\n\n## What\n\u003Ccorrected body>\n```\n\nCheck labels against `gh label list`. For a label that doesn't exist, skip it\nand suggest it in the comment (\"Suggest adding an `area:foo` label; it\ndoesn't exist yet\"). Leave `gh label create` to the maintainer, because the\nlabel set is a repo-config decision.\n\nIf the thread surfaced related issues or PRs that don't link back, draft a\none-line cross-link comment for each of them too.\n\nShow the user the drafted body, the comment, the label diff, and any\ncross-link comments, and wait for confirmation: an edit can overwrite\nframing. Then run only the commands that apply:\n\n```bash\ngh issue edit \u003C#> --body \"$(cat \u003C\u003C'EOF'\n\u003Cnew body>\nEOF\n)\"\ngh issue comment \u003C#> --body \"...\"\ngh issue edit \u003C#> --add-label \"...\" --remove-label \"...\"\ngh issue comment \u003Crelated#> --body \"Related: #\u003C#> ...\"   # per cross-link\n```\n\nDone when the confirmed changes are applied and every newly found related\nissue or PR links both ways.\n\n## 3. Reopen a closed issue\n\n1. Confirm why it closed, from the thread: the resolution comment, a label,\n   or the linked PR.\n2. If a merged PR closed it but the problem persists (a regression, a partial\n   fix, scope found after merge), read that PR's diff and comments to confirm\n   what it actually shipped. When the gap has a different root cause, a fresh\n   issue that links back is usually cleaner than a reopen: call the Skill tool\n   with \"issue-create\" instead and stop here.\n3. Draft a comment saying what changed and why the close was premature or no\n   longer applies. After a merged PR, name the gap precisely: \"PR #X shipped Y,\n   but Z still reproduces because …\".\n4. Show the user the comment, and wait for confirmation. Reopen with the\n   comment attached, so the reopen is never silent:\n\n   ```bash\n   gh issue reopen \u003C#> --comment \"...\"\n   ```\n\n5. If the scope shifted, preview the label diff and apply it.\n\nDone when the issue is open with a comment explaining why, and its labels\nmatch its scope.\n\n## Related\n\n- `issue-create` — file a new issue.\n- `issue-close` — close as resolved, superseded, or duplicate.\n- `issue-restructure` — split or merge issues.\n","# Issue Update\n\nKeep an issue accurate as understanding changes, without erasing the history\nthat produced it. A reader arriving cold should see the current truth; a\nreader following the thread should see how it got there.\n\n`\u003C#>` updates an open issue; `reopen \u003C#>` reopens a closed one with new\ncontext.\n\n## 1. Read the whole thread\n\n```bash\ngh issue view \u003C#> --json title,body,state,labels,comments\n```\n\nThe comments often hold the latest framing, so the body alone can mislead.\nNote alternative approaches, corrections, `file:line` samples, cross-links,\nand labels added after filing. `--json comments` returns at most the first\n100; for a longer thread, fetch them all so a late change of framing isn't\nmissed:\n\n```bash\ngh api --paginate \"repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fissues\u002F\u003C#>\u002Fcomments\"\n```\n\nDone when you've read every comment, and can say what the thread currently\nbelieves.\n\n## 2. Update an open issue\n\nPick the change:\n\n| Situation | Action |\n| --- | --- |\n| The original framing is wrong | Edit the body **and** comment acknowledging the change |\n| New information builds on the framing | Comment only |\n| The body is wrong but its history should stay visible | Edit the body under a \"Note:\" header; the comment links to the old framing |\n| Scope or priority shifted, the text is fine | Labels only |\n\nWhen you correct framing, say what was wrong rather than rewriting silently.\nOpen the new body with a note, so cold readers know it's current, thread\nreaders see what shifted and why, and nobody re-litigates the original:\n\n```markdown\n> **Note:** Original framing assumed all suppliers had a stable `code` field.\n> Corrected after #123: the field is nullable for legacy imports. Rewritten\n> below.\n\n## What\n\u003Ccorrected body>\n```\n\nCheck labels against `gh label list`. For a label that doesn't exist, skip it\nand suggest it in the comment (\"Suggest adding an `area:foo` label; it\ndoesn't exist yet\"). Leave `gh label create` to the maintainer, because the\nlabel set is a repo-config decision.\n\nIf the thread surfaced related issues or PRs that don't link back, draft a\none-line cross-link comment for each of them too.\n\nShow the user the drafted body, the comment, the label diff, and any\ncross-link comments, and wait for confirmation: an edit can overwrite\nframing. Then run only the commands that apply:\n\n```bash\ngh issue edit \u003C#> --body \"$(cat \u003C\u003C'EOF'\n\u003Cnew body>\nEOF\n)\"\ngh issue comment \u003C#> --body \"...\"\ngh issue edit \u003C#> --add-label \"...\" --remove-label \"...\"\ngh issue comment \u003Crelated#> --body \"Related: #\u003C#> ...\"   # per cross-link\n```\n\nDone when the confirmed changes are applied and every newly found related\nissue or PR links both ways.\n\n## 3. Reopen a closed issue\n\n1. Confirm why it closed, from the thread: the resolution comment, a label,\n   or the linked PR.\n2. If a merged PR closed it but the problem persists (a regression, a partial\n   fix, scope found after merge), read that PR's diff and comments to confirm\n   what it actually shipped. When the gap has a different root cause, a fresh\n   issue that links back is usually cleaner than a reopen: call the Skill tool\n   with \"issue-create\" instead and stop here.\n3. Draft a comment saying what changed and why the close was premature or no\n   longer applies. After a merged PR, name the gap precisely: \"PR #X shipped Y,\n   but Z still reproduces because …\".\n4. Show the user the comment, and wait for confirmation. Reopen with the\n   comment attached, so the reopen is never silent:\n\n   ```bash\n   gh issue reopen \u003C#> --comment \"...\"\n   ```\n\n5. If the scope shifted, preview the label diff and apply it.\n\nDone when the issue is open with a comment explaining why, and its labels\nmatch its scope.\n\n## Related\n\n- `issue-create` — file a new issue.\n- `issue-close` — close as resolved, superseded, or duplicate.\n- `issue-restructure` — split or merge issues.\n",{"name":5,"description":7,"allowed-tools":44,"argument-hint":45},"Bash(gh issue *), Bash(gh api *), Bash(gh label list*), Read","\u003C#> | reopen \u003C#>","main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","claude-skills\u002Fissue-update",1,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit","https:\u002F\u002Fgithub.com\u002Fdougborg","http:\u002F\u002Fdougborg.org","Platforms and Infrastructure Software Engineer","2026-11-13 07:43:37",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add dougborg\u002Fharness-kit --skill issue-update",{"tool":61,"command":62},"bunx","bunx skills add dougborg\u002Fharness-kit --skill issue-update",{"tool":64,"command":65},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill issue-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fissue-update\u002FSKILL.md",true,[],[70,89,109,141,164,181],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":39},"01M6KX4J65S5FZKMSN5DQNPSZM","teach","Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fteach\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[72,82,83,84,85,86,87,88],"lessons","you","with","learned","record","references","sessions",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":39},"01M6KX4FSSG7MHF00JDT5QT0BQ","svg-logo-designer","Generate SVG logos with multiple concepts, layouts, and color variations.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fsvg-logo-designer\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[101,102,103,104,105,106,84,107,32,108],"logo","designer","svg logo designer","SVG","color","concepts","write","generate",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":121,"publishedAt":39},"01M6KX4BD3J9MZPPSH4MENH7FP","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 \u002Fskill-writer instead.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":119,"categoryName":120,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000036","内容创作者",[122,123,124,125,126,127,128,129,22,130,131,132,133,134,135,136,137,138,139,140],"writer","documentation writer","documentation","entries","changelog","architecture","document","files","question","README","notes","code","examples","pages","for","information","guides","type","writing",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":39},"01M6KX47ZJ4ZWHDN3MY8SYAWZZ","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.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fadhd-mode\u002FSKILL.md",[],[148,149,150,151,136,152,153,84,154,155,27,156,157,158,159,160,161,162,163,133],"adhd","mode","adhd mode","next","action","kit","output","style","time","back","stop","session","reader","first","REST","harness",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":39},"01M6KX463Z6E18EPDW873GDHKB","wait-what","That last message didn't land: re-explain it with the missing context.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fwait-what\u002FSKILL.md",[],[171,172,173,84,174,175,176,177,178,179,180],"wait","wait what","re","it","missing","message","context","explain","land","last",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":39},"01M6KX43NE1NB0Y2HECY515730","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.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002FSKILL.md",[],[188,189,136,190,191,192,193,83,194,174,195,196],"to questionnaire","questionnaire","person","can","answer","meeting","make","async","decision"]