[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KX2J1Z10K4MNV9D6DFF6PV":3,"skill-same:01M6KX2J1Z10K4MNV9D6DFF6PV":74},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6KX2J1Z10K4MNV9D6DFF6PV","issue-create",null,"Files a new GitHub issue: searches for duplicates, picks focused vs umbrella scope, applies real labels, and previews before posting. Use when the user asks to file, open, or track an issue, and when another workflow needs to record deferred work, a bug found mid-task, or a follow-up as an 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\u002Fskills\u002Fproject-management\u002Fissue-create\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"create","issue create","issue","labels","workflow","for","scope","as","posting","task","files","duplicates","up","use","gh","Bash","open","gh issue","file","search","2026-11-10 10:12:30",false,"---\nname: issue-create\ndescription: >-\n  Files a new GitHub issue: searches for duplicates, picks focused vs umbrella\n  scope, applies real labels, and previews before posting. Use when the user\n  asks to file, open, or track an issue, and when another workflow needs to\n  record deferred work, a bug found mid-task, or a follow-up as an issue.\nallowed-tools: Bash(gh issue *), Bash(gh search *), Bash(gh label list*), Read\n---\n\n# Issue Create\n\nFile one issue without fragmenting a discussion that already exists. The user\nsees the title, body, and labels before anything is posted.\n\n## 1. Search for duplicates\n\n```bash\ngh search issues \"\u003Ckeywords>\" --repo \u003Cowner>\u002F\u003Crepo>\ngh issue list --repo \u003Cowner>\u002F\u003Crepo> --search \"\u003Ckeywords>\" --state all\n```\n\nRead each candidate's body and comments; a title alone misleads.\nSearch by topic, not by the title you were about to write: the same work is\noften filed under a different framing (an issue saying \"the standard is\ndocumented but unenforced\" can duplicate one saying \"set up the testing\nstack\"). Try two or three phrasings of the underlying need.\n\n- **Same work:** comment on it with your context and a cross-link instead,\n  after showing the user that comment, and stop. Fragmenting discussion\n  across near-duplicates costs more than over-linking.\n- **Adjacent but distinct:** file the new issue and cross-link both\n  directions.\n- **Unclear:** show both to the user and ask.\n\nWhen the caller names an issue as a known source (an issue being split, say),\nit is adjacent by definition: link it, and file.\n\nDone when every candidate is classed as same, adjacent, or unrelated.\n\n## 2. Decide scope\n\nFile **focused** by default: one fix, one file or tight area, one PR closes\nit. File an **umbrella**, tracked with checkboxes, when the work spans three\nor more files or domains, you expect two or more PRs against it, or triage\nneeds a single anchor for related conversations. When in doubt, file focused:\nsplitting an umbrella later is cheap, and so is merging focused issues (the\nissue-restructure skill, which the user runs).\n\nDone when you can say which shape this is and why.\n\n## 3. Pick labels\n\n```bash\ngh label list --repo \u003Cowner>\u002F\u003Crepo>\n```\n\nApply kind (`bug`, `enhancement`, `chore`), area, and priority (`p0`–`p3`)\nfrom labels that exist. When none fits, file without it and add a line to the\nbody: \"No `area:*` label exists yet; suggest creating one.\" Leave\n`gh label create` to the maintainer, because the label set is a repo-config\ndecision.\n\nDone when every label you plan to apply appears in `gh label list`.\n\n## 4. Draft and preview\n\nWrite the body: context, current behaviour, expected behaviour, `file:line`\nreferences, and cross-links to related issues and PRs. For each adjacent\nissue from step 1, draft the one-line comment that will link it back to the\nnew issue. Show the user the title, body, labels, and those link-back\ncomments.\n\nDone when the user confirms the draft.\n\n## 5. File\n\n```bash\ngh issue create --repo \u003Cowner>\u002F\u003Crepo> --title \"...\" --body \"...\" --label \"...\"\ngh issue comment \u003Cadjacent#> --repo \u003Cowner>\u002F\u003Crepo> --body \"Related: #\u003Cnew>\"   # per adjacent issue\n```\n\nDone when you've printed the new issue's URL, and every adjacent issue from\nstep 1 links back to it.\n\n## Related\n\n- `issue-close` — close as resolved, superseded, or duplicate.\n- `issue-update` — edit the body or labels, comment, reopen.\n- `issue-restructure` — split one issue into many, or merge many into one.\n- `harness-issue` — file upstream against harness-kit specifically.\n","# Issue Create\n\nFile one issue without fragmenting a discussion that already exists. The user\nsees the title, body, and labels before anything is posted.\n\n## 1. Search for duplicates\n\n```bash\ngh search issues \"\u003Ckeywords>\" --repo \u003Cowner>\u002F\u003Crepo>\ngh issue list --repo \u003Cowner>\u002F\u003Crepo> --search \"\u003Ckeywords>\" --state all\n```\n\nRead each candidate's body and comments; a title alone misleads.\nSearch by topic, not by the title you were about to write: the same work is\noften filed under a different framing (an issue saying \"the standard is\ndocumented but unenforced\" can duplicate one saying \"set up the testing\nstack\"). Try two or three phrasings of the underlying need.\n\n- **Same work:** comment on it with your context and a cross-link instead,\n  after showing the user that comment, and stop. Fragmenting discussion\n  across near-duplicates costs more than over-linking.\n- **Adjacent but distinct:** file the new issue and cross-link both\n  directions.\n- **Unclear:** show both to the user and ask.\n\nWhen the caller names an issue as a known source (an issue being split, say),\nit is adjacent by definition: link it, and file.\n\nDone when every candidate is classed as same, adjacent, or unrelated.\n\n## 2. Decide scope\n\nFile **focused** by default: one fix, one file or tight area, one PR closes\nit. File an **umbrella**, tracked with checkboxes, when the work spans three\nor more files or domains, you expect two or more PRs against it, or triage\nneeds a single anchor for related conversations. When in doubt, file focused:\nsplitting an umbrella later is cheap, and so is merging focused issues (the\nissue-restructure skill, which the user runs).\n\nDone when you can say which shape this is and why.\n\n## 3. Pick labels\n\n```bash\ngh label list --repo \u003Cowner>\u002F\u003Crepo>\n```\n\nApply kind (`bug`, `enhancement`, `chore`), area, and priority (`p0`–`p3`)\nfrom labels that exist. When none fits, file without it and add a line to the\nbody: \"No `area:*` label exists yet; suggest creating one.\" Leave\n`gh label create` to the maintainer, because the label set is a repo-config\ndecision.\n\nDone when every label you plan to apply appears in `gh label list`.\n\n## 4. Draft and preview\n\nWrite the body: context, current behaviour, expected behaviour, `file:line`\nreferences, and cross-links to related issues and PRs. For each adjacent\nissue from step 1, draft the one-line comment that will link it back to the\nnew issue. Show the user the title, body, labels, and those link-back\ncomments.\n\nDone when the user confirms the draft.\n\n## 5. File\n\n```bash\ngh issue create --repo \u003Cowner>\u002F\u003Crepo> --title \"...\" --body \"...\" --label \"...\"\ngh issue comment \u003Cadjacent#> --repo \u003Cowner>\u002F\u003Crepo> --body \"Related: #\u003Cnew>\"   # per adjacent issue\n```\n\nDone when you've printed the new issue's URL, and every adjacent issue from\nstep 1 links back to it.\n\n## Related\n\n- `issue-close` — close as resolved, superseded, or duplicate.\n- `issue-update` — edit the body or labels, comment, reopen.\n- `issue-restructure` — split one issue into many, or merge many into one.\n- `harness-issue` — file upstream against harness-kit specifically.\n",{"name":5,"description":7,"allowed-tools":44},"Bash(gh issue *), Bash(gh search *), Bash(gh label list*), Read","main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","skills\u002Fproject-management\u002Fissue-create",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add dougborg\u002Fharness-kit --skill issue-create",{"tool":60,"command":61},"bunx","bunx skills add dougborg\u002Fharness-kit --skill issue-create",{"tool":63,"command":64},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill issue-create","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fproject-management\u002Fissue-create\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",123,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fproject-management\u002Fissue-create\u002Fagents\u002Fopenai.yaml",[75,94,115,145,169,186],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"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",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[77,87,88,89,90,91,92,93],"lessons","you","with","learned","record","references","sessions",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"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",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[106,107,108,109,110,111,89,112,113,114],"logo","designer","svg logo designer","SVG","color","concepts","write","read","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":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",[121,124],{"categoryNo":122,"categoryName":123,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":125,"categoryName":126,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000036","内容创作者",[128,129,130,131,132,133,134,29,32,135,136,137,138,139,140,24,141,142,143,144],"writer","documentation writer","documentation","entries","changelog","architecture","document","question","README","notes","code","examples","pages","information","guides","type","writing",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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",[],[152,153,154,155,24,156,157,89,158,159,160,161,162,163,164,165,166,167,168,138],"adhd","mode","adhd mode","next","action","kit","output","style","progress","time","back","stop","session","reader","first","REST","harness",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"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",[],[176,177,178,89,179,180,181,182,183,184,185],"wait","wait what","re","it","missing","message","context","explain","land","last",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"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",[],[193,194,24,195,196,197,198,88,199,179,200,201],"to questionnaire","questionnaire","person","can","answer","meeting","make","async","decision"]