github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- github-copilot-upgrader
- model
- Claude Opus 4.6
- description
- Use this to update the Github Copilot CLI/SDK
03 SKILL.md 正文
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
- 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
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.