Agent skill · software engineering · microsoft
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK
Why this skill is useful
Adds a detailed upgrade process for the @github/copilot npm package, including specific commands and documentation steps that the AI wouldn't generate on its own.
What it needs
Requires npm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 188,455 stars on the source repository.
What this skill does
You are an expert at upgrading the @github/copilot npm package in the vscode-copilot-chat project. Upgrade Process You must create a TODO list of all items that are to be completed. You MUST create a TODO markdown file before commencing any of the work. Update this file after each step is completed. Complete all TODO items in sequence without stopping to ask for confirmation, only stop if you encounter any ambiguous decision that requires user input. The TODO is your primary tracking mechanism. Before each step you MUST read the TODO to determine what to do next. At a minimum your TODO must contain the following: 1. Snapshot old type definitions 2. Update the package 3. Compare differences in type definitions and document them 4. Compile, 5. fix 6. test 7. Repeat the compile, fix, and test steps until all tests pass 8. Run integration tests 9. Repeat the compile, fix, and test steps until all tests pass 11. Create a summary Note: Do not run any integration test. Follow these steps exactly: 1. Snapshot of old type definitions Take a snapshot of nodemodules/@github/copilot/sdk/index.d.ts to compare against after the upghttps://github.com/microsoft/vscode/issues/291457rade. 2. Update the package using command pnpm add @github/copilot@latest After this you MUST run pnpm run postinstall 3. Compare differences in type definitions Use mode=background for comparing the files and when done, just let me know its done This is what you need to do in the background task: Analyze the differences between the old and new index.d.ts files to identify any API changes, new features, or breaking changes. Document the changes in a clear and organized manner, create the documentation in in .build/upgrade-notes.md 4. Compile, fix and test 4.1 Compile Run the following commands to identify any type errors caused by the upgrade: You must perform a deep analysis of the compilation errors before attempting to resolve them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/github-copilot-upgrader