[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699C3JWBYPM6TKA2X20B3XJ":3,"skill-same:01M699C3JWBYPM6TKA2X20B3XJ":60},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M699C3JWBYPM6TKA2X20B3XJ","github-copilot-upgrader",null,"Use this to update the Github Copilot CLI\u002FSDK","microsoft\u002Fvscode","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK2WED5M549DX06VBCH",195270,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fextensions\u002Fcopilot\u002F.agents\u002Fskills\u002Fgithub-copilot-upgrader\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"github","github copilot upgrader","github copilot","copilot","cli","sdk","update","copilot cli","use","github copilot cli","opus","2026-11-10 10:12:30",false,"---\nname: github-copilot-upgrader\ndescription: Use this to update the Github Copilot CLI\u002FSDK\nmodel: Claude Opus 4.6\n---\n\nYou are an expert at upgrading the @github\u002Fcopilot npm package in the vscode-copilot-chat project.\n\n## Upgrade Process\n\nYou must create a TODO list of all items that are to be completed.\nYou MUST create a TODO markdown file before commencing any of the work. Update this file after each step is completed.\nComplete all TODO items in sequence without stopping to ask for confirmation, only stop if you encounter any ambiguous decision that requires user input.\nThe TODO is your primary tracking mechanism. Before each step you MUST read the TODO to determine what to do next.\n\nAt a minimum your TODO must contain the following:\n1. Snapshot old type definitions\n2. Update the package\n3. Compare differences in type definitions and document them\n4. Compile,\n5. fix\n6. test\n7. Repeat the compile, fix, and test steps until all tests pass\n8. Run integration tests\n9. Repeat the compile, fix, and test steps until all tests pass\n11. Create a summary\n\nNote:\n* Do not run any integration test.\n\nFollow these steps exactly:\n\n### 1. Snapshot of old type definitions\nTake a snapshot of node_modules\u002F@github\u002Fcopilot\u002Fsdk\u002Findex.d.ts to compare against after the upghttps:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fissues\u002F291457rade.\n\n### 2. Update the package using command `pnpm add @github\u002Fcopilot@latest`\nAfter this you MUST run `pnpm run postinstall`\n\n### 3. Compare differences in type definitions\n* Use mode=background for comparing the files and when done, just let me know its done\n* This is what you need to do in the background task:\n    - Analyze the differences between the old and new index.d.ts files to identify any API changes, new features, or breaking changes.\n    - Document the changes in a clear and organized manner, create the documentation in in .build\u002Fupgrade-notes.md\n\n\n### 4. Compile, fix and test\n\n#### 4.1 Compile\n- Run the following commands to identify any type errors caused by the upgrade:\n- You must perform a deep analysis of the compilation errors before attempting to resolve them.\n- Ensure there are no compilation errors before proceeding to run the tests.\n```bash\npnpm run postinstall\npnpm run compile\npnpm exec tsc --noEmit --project tsconfig.json\n```\n\n#### 4.2 Run Tests\n- Use the following command to run test\n```bash\npnpm run test:unit\n```\n- Do NOT change the behavior of the code just to make the tests pass.\nIf the upgrade causes a test to fail, you must analyze the failure and determine if it is due to a legitimate issue caused by the upgrade or if it is a problem with the test itself.\n- Ensure all tests are passing before proceeding to the next step.\n\n#### 5. Summarize the changes\n\n- After successfully upgrading the @github\u002Fcopilot package and ensuring that all tests are passing, you must create a summary of the changes that were made during the upgrade process.\n- Give a summary of the changes in the code base\n- Give a summary of the changes in the tests\n- Give a summary of the differences in the type definitions between the old and new versions of the @github\u002Fcopilot package.\n  - Focus on the new API or features that were added, any breaking changes that were introduced, and any deprecated features that were removed.\n- Document the summary in a clear and organized manner, create the documentation in in .build\u002Fupgrade-notes.md\n","You are an expert at upgrading the @github\u002Fcopilot npm package in the vscode-copilot-chat project.\n\n## Upgrade Process\n\nYou must create a TODO list of all items that are to be completed.\nYou MUST create a TODO markdown file before commencing any of the work. Update this file after each step is completed.\nComplete all TODO items in sequence without stopping to ask for confirmation, only stop if you encounter any ambiguous decision that requires user input.\nThe TODO is your primary tracking mechanism. Before each step you MUST read the TODO to determine what to do next.\n\nAt a minimum your TODO must contain the following:\n1. Snapshot old type definitions\n2. Update the package\n3. Compare differences in type definitions and document them\n4. Compile,\n5. fix\n6. test\n7. Repeat the compile, fix, and test steps until all tests pass\n8. Run integration tests\n9. Repeat the compile, fix, and test steps until all tests pass\n11. Create a summary\n\nNote:\n* Do not run any integration test.\n\nFollow these steps exactly:\n\n### 1. Snapshot of old type definitions\nTake a snapshot of node_modules\u002F@github\u002Fcopilot\u002Fsdk\u002Findex.d.ts to compare against after the upghttps:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fissues\u002F291457rade.\n\n### 2. Update the package using command `pnpm add @github\u002Fcopilot@latest`\nAfter this you MUST run `pnpm run postinstall`\n\n### 3. Compare differences in type definitions\n* Use mode=background for comparing the files and when done, just let me know its done\n* This is what you need to do in the background task:\n    - Analyze the differences between the old and new index.d.ts files to identify any API changes, new features, or breaking changes.\n    - Document the changes in a clear and organized manner, create the documentation in in .build\u002Fupgrade-notes.md\n\n\n### 4. Compile, fix and test\n\n#### 4.1 Compile\n- Run the following commands to identify any type errors caused by the upgrade:\n- You must perform a deep analysis of the compilation errors before attempting to resolve them.\n- Ensure there are no compilation errors before proceeding to run the tests.\n```bash\npnpm run postinstall\npnpm run compile\npnpm exec tsc --noEmit --project tsconfig.json\n```\n\n#### 4.2 Run Tests\n- Use the following command to run test\n```bash\npnpm run test:unit\n```\n- Do NOT change the behavior of the code just to make the tests pass.\nIf the upgrade causes a test to fail, you must analyze the failure and determine if it is due to a legitimate issue caused by the upgrade or if it is a problem with the test itself.\n- Ensure all tests are passing before proceeding to the next step.\n\n#### 5. Summarize the changes\n\n- After successfully upgrading the @github\u002Fcopilot package and ensuring that all tests are passing, you must create a summary of the changes that were made during the upgrade process.\n- Give a summary of the changes in the code base\n- Give a summary of the changes in the tests\n- Give a summary of the differences in the type definitions between the old and new versions of the @github\u002Fcopilot package.\n  - Focus on the new API or features that were added, any breaking changes that were introduced, and any deprecated features that were removed.\n- Document the summary in a clear and organized manner, create the documentation in in .build\u002Fupgrade-notes.md\n",{"name":5,"model":35,"description":7},"Claude Opus 4.6","main","d2b1bf2230b505648e972e81d854743de79b65af","extensions\u002Fcopilot\u002F.agents\u002Fskills\u002Fgithub-copilot-upgrader",43791,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode","https:\u002F\u002Fcode.visualstudio.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 03:13:10",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add microsoft\u002Fvscode --skill github-copilot-upgrader",{"tool":52,"command":53},"bunx","bunx skills add microsoft\u002Fvscode --skill github-copilot-upgrader",{"tool":55,"command":56},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill github-copilot-upgrader","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fextensions\u002Fcopilot\u002F.agents\u002Fskills\u002Fgithub-copilot-upgrader\u002FSKILL.md",true,[],[61,88,109,123,138,154],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":30},"01M70H0ANBKZAVEP1NVV4K28M3","sweeper-query","Answer natural-language questions about the VS Code Sweeper's published issue index (index-\u003Cname>.json for microsoft\u002Fvscode and the enrolled family repos) — which issues are agent-ready to implement or plan, what the sweeper proposed for an assignee or area, whether the sweeper knows a report as a duplicate, the highest-value open bugs in a lane — and, for one issue, the review's full record (evidence with file citations, fix brief, proposed comment). Use ONLY when the request explicitly names the sweeper — \"sweeper\", \"vscodesweeper\", \"sweeper-query\", a sweeper verdict, record, brief or index, an agent-ready issue — or asks what \"the sweeper\" found, proposed or knows. Do NOT use for general questions about issues, duplicates, priorities or ranking that do not mention the sweeper. Read-only; discovery only.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsweeper-query\u002FSKILL.md",[],[68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87],"sweeper query","query","sweeper","review","fix","when","request","which","natural-language","ranking","duplicates","ready","only","read","plan","open","Citations","brief","issues","code",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":30},"01M699DRJS4YJCV600Q72SVVWE","update-skills","Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says \"learn!\", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\u002FSKILL.md",[],[25,95,96,97,98,99,100,27,101,102,103,104,105,106,107,108,73],"update skills","for","pattern","domain","learnings","reusable","session","user","instructions","knowledge","repository","learn","create","sessions",{"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":115,"publishedAt":30},"01M699DPWHZ72B66P82EW31RNE","update-pr","Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-pr\u002FSKILL.md",[],[25,116,117,73,74,118,96,27,101,102,119,120,121,122],"pr","update pr","Existing","push","pull","pull request","changes",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":30},"01M699DJMR6CE1MH5XCJZ0GFQ0","sync","Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\u002FSKILL.md",[],[125,130,131,119,120,132,73,122,133,134,135,136,27,101,102,137],"SET","publish","rebase","latest","with","remote","upstream","branch",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":30},"01M699DGXHX6A2A72X57R6GGHJ","sync-upstream","Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync-upstream\u002FSKILL.md",[],[136,125,145,146,73,147,148,122,133,149,150,151,152,27,101,137,153,25],"sync upstream","fit","catch","catch up","origin","conflicts","stale","up","work",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":30},"01M699DEXYFWDGW0BAXJ5QQ377","merge","Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fmerge\u002FSKILL.md",[],[156,101,27,153,137,102,73,161,162,122],"back","base"]