mcpbeat Sign in

Github Copilot Upgrader Agent Skill

Use this to update the Github Copilot CLI/SDK

844 tokens
context cost
SKILL.md, read when the skill is used
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
188 278
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/vscode --skill github-copilot-upgrader

The instruction itself

8 sections, as written by the author

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:

  • Snapshot old type definitions
  • Update the package
  • Compare differences in type definitions and document them
  • Compile,
  • fix
  • test
  • Repease steps Compile, fix and tests until all tests are passing
  • Run integration tests
  • Repeate Compile, Fix, Test, until all tests are passing

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 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

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×16

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

2.3k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×9

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1.1k tokens
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

3.4k tokens scripts
Vercel React Best Practices
by ratacat
×7

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

1.3k tokens
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

1.1k tokens
Using Git Worktrees
by ZhanlinCui
×6

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1.4k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

1k tokens

How to use it

Copy the folder

Take microsoft/github-copilot-upgrader from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm, npx. Without those the skill loads but fails at the first command.