[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7355JBSBYP7AQQ2165FJKBW":3,"skill-same:01M7355JBSBYP7AQQ2165FJKBW":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":48},"01M7355JBSBYP7AQQ2165FJKBW","migrate-discussion",null,"Move items between Issues and Discussions.","Morrison-Lab\u002Fai-config","Morrison-Lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104235520?v=4","01M734G0451S2G35MN4HFQK7XP","Morrison Lab","01M734G059BYFDFQA8YTPDGPMH",4,"MIT","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-discussion\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: migrate-discussion\ndescription: \"Move items between Issues and Discussions.\"\nuser-invocable: true\nallowed-tools:\n  - Bash\n  - Read\n---\n\n# migrate-discussion — move items between Discussions and Issues\n\nMove a topic to the tracker where it belongs: a discussion that turned into a\nconcrete bug\u002Ftask should become an **Issue**; an issue that's really a question,\nidea, or support request should become a **Discussion**. Migration is a judgement\ncall — the \"when helpful\" part matters as much as the mechanics.\n\n## When this fires\n\n- User says \"convert this issue to a discussion\", \"move #N to Discussions\"\n- User says \"this discussion is really a bug — make it an issue\", \"open an issue\n  from discussion #N\"\n- While triaging: an issue is generating open-ended debate with no actionable\n  scope, or a discussion has converged on a concrete task someone will do\n\nDon't migrate just because a thread is long. Migrate only when the item is\nclearly in the wrong tracker.\n\n## Decide first — is a move actually warranted?\n\n| Move it **discussion → issue** when… | Move it **issue → discussion** when… |\n|---|---|\n| It's a concrete, reproducible bug | It's an open-ended question or support request |\n| It's an actionable task with a clear \"done\" | It's brainstorming \u002F a feature idea with no decision |\n| Maintainers have decided to act on it | It needs community input before any work |\n| It needs an assignee, label, milestone, or board | It has no actionable scope and no owner |\n\nLeave it where it is when it's borderline, when both trackers fit, or when the\nthread is active and a move would disrupt it. When unsure, ask the user — don't\nmigrate on a hunch.\n\n## Prefer GitHub's native convert feature\n\nGitHub has built-in one-click conversions, and they're the **best** path because\nthey preserve the original author, the full comment thread, and post an automatic\ncross-reference:\n\n- **Issue → Discussion:** on the issue, use the **\"Convert to discussion\"** menu\n  item (issue sidebar \u002F `...` menu), pick a category.\n- **Discussion → Issue:** on the discussion, use **\"Create issue from\n  discussion\"** (discussion `...` menu).\n\nThere is **no GraphQL mutation or `gh` subcommand** for either conversion — they\nare UI-only. So when you (or the user) can reach the web UI, that's the move:\npoint the user at the button, or walk them through it, and you're done.\n\nUse the recreate procedure below only when the native UI path isn't usable\n(scripted\u002Fheadless context, or the user explicitly wants it rebuilt).\n\n## Fallback — recreate and cross-link\n\nWhen you can't use the native convert feature, create the new item by hand,\npreserve attribution, cross-link both ways, and close the original with a\npointer. Get the user's approval on the drafted new item before creating it —\nthis is outward-facing and hard to reverse.\n\n### Discussion → Issue\n\n1. Read the source discussion (see the **[discussions](..\u002Fdiscussions\u002FSKILL.md)**\n   skill's read query) to capture its title, body, author, URL, and key\n   comments.\n2. Create the issue, quoting the original and linking back so authorship and\n   context aren't lost:\n\n   ```bash\n   gh issue create \\\n     --title '\u003Coriginal title>' \\\n     --label P2 \\\n     --body 'Migrated from discussion \u003Curl> (opened by @\u003Cauthor>).\n\n   \u003Coriginal body, quoted>\n\n   Key points from the discussion thread:\n   - @\u003Clogin>: \u003Csummary>'   # CREATE_ISSUE\n   ```\n\n   In a remote\u002Fweb session, use `mcp__github__issue_write` (`method: create`)\n   with the same body instead of `gh`.\n   Set the priority (`P2` is the default) per\n   [`issue-first`](..\u002F..\u002Fshared\u002Fworkflow\u002Fissue-first.md); the issue quotes\n   human content, so it takes no `ai-authored` or model label.\n   Where the repo has no `P2` label yet, create it first\n   ([`label-agent-filed-issues`](..\u002F..\u002Fshared\u002Fworkflow\u002Flabel-agent-filed-issues.md)).\n3. Comment on the discussion pointing at the new issue, then close it:\n\n   ```bash\n   gh api graphql -f discussionId='\u003Cdiscussion-id>' -f body='Moved to \u003Cissue-url> to track the actionable work.\n\n   _Posted by Claude Code (AI agent) --- not written by a human._' -f query='\n     mutation($discussionId: ID!, $body: String!) {\n       addDiscussionComment(input: {discussionId: $discussionId, body: $body}) {\n         comment { url }\n       }\n     }'   # COMMENT_DISCUSSION\n\n   gh api graphql -f discussionId='\u003Cdiscussion-id>' -f query='\n     mutation($discussionId: ID!) {\n       closeDiscussion(input: {discussionId: $discussionId, reason: OUTDATED}) {\n         discussion { url closed }\n       }\n     }'   # CLOSE_DISCUSSION\n   ```\n\n   `closeDiscussion` reasons are `RESOLVED`, `OUTDATED`, or `DUPLICATE`; use\n   `OUTDATED` for a plain move.\n\n### Issue → Discussion\n\n1. Read the source issue (`gh issue view \u003CN>` — `VIEW_ISSUE` — or\n   `mcp__github__issue_read`) for its title, body, author, URL, and comments.\n2. Look up the repository node ID and the target category ID (only certain\n   categories exist per repo):\n\n   ```bash\n   gh api graphql -f owner='\u003Cowner>' -f repo='\u003Crepo>' -f query='\n     query($owner: String!, $repo: String!) {\n       repository(owner: $owner, name: $repo) {\n         id\n         discussionCategories(first: 20) { nodes { id name isAnswerable } }\n       }\n     }'\n   ```\n\n3. Create the discussion, quoting the original and linking back:\n\n   ```bash\n   gh api graphql -f repositoryId='\u003Crepo-id>' -f categoryId='\u003Ccategory-id>' -f title='\u003Coriginal title>' -f body='Migrated from issue \u003Curl> (opened by @\u003Cauthor>).\n\n   \u003Coriginal body, quoted>' -f query='\n     mutation($repositoryId: ID!, $categoryId: ID!, $title: String!, $body: String!) {\n       createDiscussion(input: {repositoryId: $repositoryId, categoryId: $categoryId, title: $title, body: $body}) {\n         discussion { number url }\n       }\n     }'   # CREATE_DISCUSSION\n   ```\n\n4. Comment on the issue pointing at the new discussion, then close the issue as\n   not planned:\n\n   ```bash\n   gh issue comment \u003CN> --body 'Moved to \u003Cdiscussion-url> — this is better suited to Discussions.\n\n   _Posted by Claude Code (AI agent) --- not written by a human._'   # COMMENT_ISSUE\n   gh issue close \u003CN> --reason 'not planned'   # CLOSE_ISSUE\n   ```\n\n   In a remote\u002Fweb session, use `mcp__github__add_issue_comment` and\n   `mcp__github__issue_write` (`method: update`, `state: closed`,\n   `state_reason: not_planned`).\n\n## Report back\n\nGive the user both links (old and new) as clickable markdown links, say which\ndirection the migration went, and confirm the original was closed with a pointer.\n\n## Relationship to other skills\n\n- **[discussions](..\u002Fdiscussions\u002FSKILL.md)** — reads\u002Fanswers discussion topics;\n  this skill reuses its read query and hands topics back to it when a reply (not\n  a move) is the right response.\n- **[defer-issue](..\u002Fdefer-issue\u002FSKILL.md)** — files a fresh follow-up issue for\n  out-of-scope work; this skill *moves* an existing item between trackers.\n- **[sup](..\u002Fsup\u002FSKILL.md)** — routes a report to the right destination\n  (issue vs Discussions) on an *upstream* repo; same tracker-fit judgement, other\n  people's repo.\n\n## Anti-patterns\n\n- ❌ Hand-rebuilding when the native **\"Convert to discussion\"** \u002F\n  **\"Create issue from discussion\"** button would do it — the native path keeps\n  authorship, the thread, and cross-links; the fallback loses per-comment\n  authorship.\n- ❌ Migrating without cross-linking both ways — always leave a pointer on the\n  original and reference the original in the new item.\n- ❌ Closing the original **before** the new item exists — create first, link,\n  then close, so nothing is orphaned.\n- ❌ Creating the new item without the user's approval — outward-facing and hard\n  to reverse.\n- ❌ Migrating a borderline item on a hunch — when both trackers fit, leave it\n  and ask.\n","# migrate-discussion — move items between Discussions and Issues\n\nMove a topic to the tracker where it belongs: a discussion that turned into a\nconcrete bug\u002Ftask should become an **Issue**; an issue that's really a question,\nidea, or support request should become a **Discussion**. Migration is a judgement\ncall — the \"when helpful\" part matters as much as the mechanics.\n\n## When this fires\n\n- User says \"convert this issue to a discussion\", \"move #N to Discussions\"\n- User says \"this discussion is really a bug — make it an issue\", \"open an issue\n  from discussion #N\"\n- While triaging: an issue is generating open-ended debate with no actionable\n  scope, or a discussion has converged on a concrete task someone will do\n\nDon't migrate just because a thread is long. Migrate only when the item is\nclearly in the wrong tracker.\n\n## Decide first — is a move actually warranted?\n\n| Move it **discussion → issue** when… | Move it **issue → discussion** when… |\n|---|---|\n| It's a concrete, reproducible bug | It's an open-ended question or support request |\n| It's an actionable task with a clear \"done\" | It's brainstorming \u002F a feature idea with no decision |\n| Maintainers have decided to act on it | It needs community input before any work |\n| It needs an assignee, label, milestone, or board | It has no actionable scope and no owner |\n\nLeave it where it is when it's borderline, when both trackers fit, or when the\nthread is active and a move would disrupt it. When unsure, ask the user — don't\nmigrate on a hunch.\n\n## Prefer GitHub's native convert feature\n\nGitHub has built-in one-click conversions, and they're the **best** path because\nthey preserve the original author, the full comment thread, and post an automatic\ncross-reference:\n\n- **Issue → Discussion:** on the issue, use the **\"Convert to discussion\"** menu\n  item (issue sidebar \u002F `...` menu), pick a category.\n- **Discussion → Issue:** on the discussion, use **\"Create issue from\n  discussion\"** (discussion `...` menu).\n\nThere is **no GraphQL mutation or `gh` subcommand** for either conversion — they\nare UI-only. So when you (or the user) can reach the web UI, that's the move:\npoint the user at the button, or walk them through it, and you're done.\n\nUse the recreate procedure below only when the native UI path isn't usable\n(scripted\u002Fheadless context, or the user explicitly wants it rebuilt).\n\n## Fallback — recreate and cross-link\n\nWhen you can't use the native convert feature, create the new item by hand,\npreserve attribution, cross-link both ways, and close the original with a\npointer. Get the user's approval on the drafted new item before creating it —\nthis is outward-facing and hard to reverse.\n\n### Discussion → Issue\n\n1. Read the source discussion (see the **[discussions](..\u002Fdiscussions\u002FSKILL.md)**\n   skill's read query) to capture its title, body, author, URL, and key\n   comments.\n2. Create the issue, quoting the original and linking back so authorship and\n   context aren't lost:\n\n   ```bash\n   gh issue create \\\n     --title '\u003Coriginal title>' \\\n     --label P2 \\\n     --body 'Migrated from discussion \u003Curl> (opened by @\u003Cauthor>).\n\n   \u003Coriginal body, quoted>\n\n   Key points from the discussion thread:\n   - @\u003Clogin>: \u003Csummary>'   # CREATE_ISSUE\n   ```\n\n   In a remote\u002Fweb session, use `mcp__github__issue_write` (`method: create`)\n   with the same body instead of `gh`.\n   Set the priority (`P2` is the default) per\n   [`issue-first`](..\u002F..\u002Fshared\u002Fworkflow\u002Fissue-first.md); the issue quotes\n   human content, so it takes no `ai-authored` or model label.\n   Where the repo has no `P2` label yet, create it first\n   ([`label-agent-filed-issues`](..\u002F..\u002Fshared\u002Fworkflow\u002Flabel-agent-filed-issues.md)).\n3. Comment on the discussion pointing at the new issue, then close it:\n\n   ```bash\n   gh api graphql -f discussionId='\u003Cdiscussion-id>' -f body='Moved to \u003Cissue-url> to track the actionable work.\n\n   _Posted by Claude Code (AI agent) --- not written by a human._' -f query='\n     mutation($discussionId: ID!, $body: String!) {\n       addDiscussionComment(input: {discussionId: $discussionId, body: $body}) {\n         comment { url }\n       }\n     }'   # COMMENT_DISCUSSION\n\n   gh api graphql -f discussionId='\u003Cdiscussion-id>' -f query='\n     mutation($discussionId: ID!) {\n       closeDiscussion(input: {discussionId: $discussionId, reason: OUTDATED}) {\n         discussion { url closed }\n       }\n     }'   # CLOSE_DISCUSSION\n   ```\n\n   `closeDiscussion` reasons are `RESOLVED`, `OUTDATED`, or `DUPLICATE`; use\n   `OUTDATED` for a plain move.\n\n### Issue → Discussion\n\n1. Read the source issue (`gh issue view \u003CN>` — `VIEW_ISSUE` — or\n   `mcp__github__issue_read`) for its title, body, author, URL, and comments.\n2. Look up the repository node ID and the target category ID (only certain\n   categories exist per repo):\n\n   ```bash\n   gh api graphql -f owner='\u003Cowner>' -f repo='\u003Crepo>' -f query='\n     query($owner: String!, $repo: String!) {\n       repository(owner: $owner, name: $repo) {\n         id\n         discussionCategories(first: 20) { nodes { id name isAnswerable } }\n       }\n     }'\n   ```\n\n3. Create the discussion, quoting the original and linking back:\n\n   ```bash\n   gh api graphql -f repositoryId='\u003Crepo-id>' -f categoryId='\u003Ccategory-id>' -f title='\u003Coriginal title>' -f body='Migrated from issue \u003Curl> (opened by @\u003Cauthor>).\n\n   \u003Coriginal body, quoted>' -f query='\n     mutation($repositoryId: ID!, $categoryId: ID!, $title: String!, $body: String!) {\n       createDiscussion(input: {repositoryId: $repositoryId, categoryId: $categoryId, title: $title, body: $body}) {\n         discussion { number url }\n       }\n     }'   # CREATE_DISCUSSION\n   ```\n\n4. Comment on the issue pointing at the new discussion, then close the issue as\n   not planned:\n\n   ```bash\n   gh issue comment \u003CN> --body 'Moved to \u003Cdiscussion-url> — this is better suited to Discussions.\n\n   _Posted by Claude Code (AI agent) --- not written by a human._'   # COMMENT_ISSUE\n   gh issue close \u003CN> --reason 'not planned'   # CLOSE_ISSUE\n   ```\n\n   In a remote\u002Fweb session, use `mcp__github__add_issue_comment` and\n   `mcp__github__issue_write` (`method: update`, `state: closed`,\n   `state_reason: not_planned`).\n\n## Report back\n\nGive the user both links (old and new) as clickable markdown links, say which\ndirection the migration went, and confirm the original was closed with a pointer.\n\n## Relationship to other skills\n\n- **[discussions](..\u002Fdiscussions\u002FSKILL.md)** — reads\u002Fanswers discussion topics;\n  this skill reuses its read query and hands topics back to it when a reply (not\n  a move) is the right response.\n- **[defer-issue](..\u002Fdefer-issue\u002FSKILL.md)** — files a fresh follow-up issue for\n  out-of-scope work; this skill *moves* an existing item between trackers.\n- **[sup](..\u002Fsup\u002FSKILL.md)** — routes a report to the right destination\n  (issue vs Discussions) on an *upstream* repo; same tracker-fit judgement, other\n  people's repo.\n\n## Anti-patterns\n\n- ❌ Hand-rebuilding when the native **\"Convert to discussion\"** \u002F\n  **\"Create issue from discussion\"** button would do it — the native path keeps\n  authorship, the thread, and cross-links; the fallback loses per-comment\n  authorship.\n- ❌ Migrating without cross-linking both ways — always leave a pointer on the\n  original and reference the original in the new item.\n- ❌ Closing the original **before** the new item exists — create first, link,\n  then close, so nothing is orphaned.\n- ❌ Creating the new item without the user's approval — outward-facing and hard\n  to reverse.\n- ❌ Migrating a borderline item on a hunch — when both trackers fit, leave it\n  and ask.\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":27},[25,26],"Bash","Read",true,"main","f8f5ea79cc52e903c30773b5e264e384e715c4c7","skills\u002Fmigrate-discussion",1,"https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config","https:\u002F\u002Fmorrison-lab.github.io\u002Fai-config\u002F","https:\u002F\u002Fgithub.com\u002FMorrison-Lab","2026-11-12 06:23:19",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":27},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Morrison-Lab\u002Fai-config --skill migrate-discussion",{"tool":42,"command":43},"bunx","bunx skills add Morrison-Lab\u002Fai-config --skill migrate-discussion",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Morrison-Lab\u002Fai-config --skill migrate-discussion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-discussion\u002FSKILL.md",[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M735B6T9KP24YK73HZYS361B","triage","Triage backlog: P1\u002FP2\u002FP3 or close.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M735ABCWNZ3WJKPC1ABJ7W8B","st","Start task issue-first.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fst\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7355RRVTEEFJ16QVM86EK7X","mwc","Session merge grant with confidence gate.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fmwc\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M73558FN1TYWMMRZYJQSTAK8","memorize","Persist memory across sessions.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fmemorize\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7351KXGW9QTKQHH1HJFS4YF","defer-issue","File issue for deferred work.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fdefer-issue\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M73512AEG0J04NPM2YP9CEW8","create-release-checklist","Create an R package release-checklist issue.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-release-checklist\u002FSKILL.md",[],[]]