New to Claude Skills? Learn how to install them →

Gmicrosoft on GitHub

GitHub Copilot Upgrader

OfficialFree

Streamline the upgrade process for GitHub Copilot CLI/SDK.

by microsoft188.6k stars on microsoft/vscode
2 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What GitHub Copilot Upgrader does

The GitHub Copilot Upgrader is a specialized tool designed to facilitate the upgrade of the @github/copilot npm package within the vscode-copilot-chat project. This skill automates the tedious aspects of the upgrade process, ensuring that developers can efficiently manage updates without losing track of essential steps. By following a structured TODO list, the upgrader guides users through each phase of the upgrade, from snapshotting old type definitions to documenting changes post-upgrade.

Upon initiating the upgrade, the first task is to create a comprehensive TODO markdown file that outlines the steps required for the upgrade. This includes taking a snapshot of the existing type definitions, updating the package using npm, and comparing the differences in type definitions to identify any API changes. The upgrader emphasizes the importance of thorough documentation, ensuring that users can easily reference the changes made during the upgrade process.

The skill also incorporates a systematic approach to compiling, fixing, and testing the upgraded package. Users are instructed to run specific commands to identify type errors and execute unit tests, with a strong focus on maintaining the integrity of the code. The process is iterative, requiring users to repeat compilation and testing until all tests pass, thus ensuring a stable upgrade.

Finally, the upgrader culminates in a detailed summary of the changes made, including modifications to the codebase, updates to tests, and differences in type definitions. This structured approach not only simplifies the upgrade process but also provides clarity on the implications of the upgrade, making it an essential tool for developers working with GitHub Copilot.

When to use it

Use this tool when you need to upgrade the GitHub Copilot npm package in your project and want to ensure a systematic approach to the process.

When not to use it

This skill is not suitable for users who require a one-click upgrade solution or those unfamiliar with npm commands and TypeScript type definitions.

What you can build with it

Upgrading for New Features

When new features are released in the GitHub Copilot package, use this skill to ensure a smooth upgrade.

Maintaining Compatibility

Regularly upgrade the package to maintain compatibility with the latest APIs and avoid deprecated features.

Documenting Changes

Use the skill to generate organized documentation of changes made during the upgrade, aiding future reference.

How to install GitHub Copilot Upgrader

View source

1. Install with the skills CLI

npx skills add microsoft/vscode/github-copilot-upgrader --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by microsoft

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. Repease steps Compile, fix and tests until all tests are passing
  8. Run integration tests
  9. Repeate Compile, Fix, Test, until all tests are passing
  10. Create a summary

Note:

  • Do not run any integration test.

Follow these steps exactly:

1. Snapshot of old type definitions

Take a snapshot of node_modules/@github/copilot/sdk/index.d.ts to compare against after the upghttps://github.com/microsoft/vscode/issues/291457rade.

2. Update the package using command npm install @github/copilot@latest

After this you MSUT run npm 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.
  • Ensure there are no compilation errors before proceeding to run the tests.
npm run postinstall
npm run compile
npx tsc --noEmit --project tsconfig.json

4.2 Run Tests

  • Use the following command to run test
npm run test:unit
  • Do NOT change the behavour of the code just to make the tests pass. If 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.
  • Ensure all tests are passing before proceeding to the next step.

5. Summarize the changes

  • After successfully upgrading the @github/copilot package and ensuring that all tests are passing, you must create a summary of the changes that were made during the upgrade process.
  • Give a summary of the changes in the code base
  • Give a summary of the changes in the tests
  • Give a summary of the differenes in the type definitions between the old and new versions of the @github/copilot package.
    • Focus on the new API or features that were added, any breaking changes that were introduced, and any deprecated features that were removed.
  • Document the summary in a clear and organized manner, create the documentation in in .build/upgrade-notes.md

Frequently asked questions about GitHub Copilot Upgrader

Similar skills