[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KX083804TF09EX43588X0R":3,"skill-same:01M6KX083804TF09EX43588X0R":75},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6KX083804TF09EX43588X0R","pr-comments",null,"Reply in thread to every unresolved PR review comment, once the fixes are pushed.","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\u002Fskills\u002Fengineering\u002Fpr-comments\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"pr","comments","pr comments","gh","fixes","thread","threads","scripts","shared","reply","read","review","gh pr","Bash","api","git","pr review","2026-11-10 10:12:30",false,"---\nname: pr-comments\ndescription: Reply in thread to every unresolved PR review comment, once the fixes are pushed.\nallowed-tools: Bash(gh api *), Bash(gh pr *), Bash(git *), Bash(\u003Cshared-scripts-dir>\u002Fpr-threads.sh*), Read\n---\n\n# PR Comments\n\nAnswer every unresolved review comment on a PR, in its own thread. This is\nthe reply pass: the fixes are already made and pushed. To fix and reply in\none go, use `\u002Freview-pr` instead.\n\nReply only after the push has landed, since each reply tells the reviewer the\nfix is live. Reply only through `pr-threads.sh … reply`: it checks the comment\nbelongs to this PR and uses the right endpoint. `gh pr comment` posts outside\nthe thread and loses its context, and the\n`gh api ...\u002Fpulls\u002Fcomments\u002F{id}\u002Freplies` endpoint does not exist (404).\n\n## 1. Fetch the unresolved comments\n\n```bash\n\u003Cshared-scripts-dir>\u002Fpr-threads.sh \u003CPR#> context\n```\n\nThe script returns comments with their resolved status. Done when you have\nthe unresolved ones listed.\n\n## 2. Triage each comment\n\nGive each one an answer:\n\n- **Fixed:** \"Fixed — [what changed]\"\n- **Already fixed** in an earlier commit: \"Addressed in [commit] — [brief\n  explanation]\"\n- **Acknowledged** but deferred: \"Noted — [reasoning]. Tracked in #NNN\",\n  with the issue link\n\nSeveral small, related comments from one reviewer can share one numbered\nreply; several comments in one thread get one reply. Agree conflicting\nfeedback before replying. [reply-patterns.md](reply-patterns.md) has worked\nexamples, batching rules, and how to handle disagreement, multiple reviewers,\nand declined suggestions.\n\nDone when every unresolved comment has a drafted answer.\n\n## 3. Reply in thread\n\n```bash\n\u003Cshared-scripts-dir>\u002Fpr-threads.sh \u003CPR#> reply \u003Ccomment_id> 'Fixed — [explanation]'\n```\n\nReply to every comment in the same push cycle. Done when every unresolved\ncomment from step 1 has a reply.\n\n## 4. Summary\n\nReport the counts fixed, already fixed, and acknowledged, plus anything left\nunaddressed. Done when the report is printed.\n\n## Related\n\n- `\u002Freview-pr` — review a PR, or fix and reply to its feedback\n- `\u002Fcommit` — create the commits being replied to\n- [GitHub REST API: Pull Request Comments](https:\u002F\u002Fdocs.github.com\u002Fen\u002Frest\u002Fpulls\u002Fcomments)\n","# PR Comments\n\nAnswer every unresolved review comment on a PR, in its own thread. This is\nthe reply pass: the fixes are already made and pushed. To fix and reply in\none go, use `\u002Freview-pr` instead.\n\nReply only after the push has landed, since each reply tells the reviewer the\nfix is live. Reply only through `pr-threads.sh … reply`: it checks the comment\nbelongs to this PR and uses the right endpoint. `gh pr comment` posts outside\nthe thread and loses its context, and the\n`gh api ...\u002Fpulls\u002Fcomments\u002F{id}\u002Freplies` endpoint does not exist (404).\n\n## 1. Fetch the unresolved comments\n\n```bash\n\u003Cshared-scripts-dir>\u002Fpr-threads.sh \u003CPR#> context\n```\n\nThe script returns comments with their resolved status. Done when you have\nthe unresolved ones listed.\n\n## 2. Triage each comment\n\nGive each one an answer:\n\n- **Fixed:** \"Fixed — [what changed]\"\n- **Already fixed** in an earlier commit: \"Addressed in [commit] — [brief\n  explanation]\"\n- **Acknowledged** but deferred: \"Noted — [reasoning]. Tracked in #NNN\",\n  with the issue link\n\nSeveral small, related comments from one reviewer can share one numbered\nreply; several comments in one thread get one reply. Agree conflicting\nfeedback before replying. [reply-patterns.md](reply-patterns.md) has worked\nexamples, batching rules, and how to handle disagreement, multiple reviewers,\nand declined suggestions.\n\nDone when every unresolved comment has a drafted answer.\n\n## 3. Reply in thread\n\n```bash\n\u003Cshared-scripts-dir>\u002Fpr-threads.sh \u003CPR#> reply \u003Ccomment_id> 'Fixed — [explanation]'\n```\n\nReply to every comment in the same push cycle. Done when every unresolved\ncomment from step 1 has a reply.\n\n## 4. Summary\n\nReport the counts fixed, already fixed, and acknowledged, plus anything left\nunaddressed. Done when the report is printed.\n\n## Related\n\n- `\u002Freview-pr` — review a PR, or fix and reply to its feedback\n- `\u002Fcommit` — create the commits being replied to\n- [GitHub REST API: Pull Request Comments](https:\u002F\u002Fdocs.github.com\u002Fen\u002Frest\u002Fpulls\u002Fcomments)\n",{"name":5,"description":7,"allowed-tools":41},"Bash(gh api *), Bash(gh pr *), Bash(git *), Bash(\u003Cshared-scripts-dir>\u002Fpr-threads.sh*), Read","main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","skills\u002Fengineering\u002Fpr-comments",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add dougborg\u002Fharness-kit --skill pr-comments",{"tool":57,"command":58},"bunx","bunx skills add dougborg\u002Fharness-kit --skill pr-comments",{"tool":60,"command":61},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill pr-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fpr-comments\u002FSKILL.md",true,[65,71],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",154,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fpr-comments\u002Fagents\u002Fopenai.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"reply-patterns.md",3289,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fpr-comments\u002Freply-patterns.md",[76,95,115,148,172,189],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":36},"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",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[78,88,89,90,91,92,93,94],"lessons","you","with","learned","record","references","sessions",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":36},"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",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[107,108,109,110,111,112,90,113,29,114],"logo","designer","svg logo designer","SVG","color","concepts","write","generate",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":127,"publishedAt":36},"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",[121,124],{"categoryNo":122,"categoryName":123,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":125,"categoryName":126,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000036","内容创作者",[128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147],"writer","documentation writer","documentation","entries","changelog","architecture","document","files","use","question","README","notes","code","examples","pages","for","information","guides","type","writing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":36},"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",[],[155,156,157,158,143,159,160,90,161,162,163,164,165,166,167,168,169,170,171,140],"adhd","mode","adhd mode","next","action","kit","output","style","progress","time","back","stop","session","reader","first","REST","harness",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":36},"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",[],[179,180,181,90,182,183,184,185,186,187,188],"wait","wait what","re","it","missing","message","context","explain","land","last",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":36},"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",[],[196,197,143,198,199,200,201,89,202,182,203,204],"to questionnaire","questionnaire","person","can","answer","meeting","make","async","decision"]