github-copilot-upgrader

Upgrades the @github/copilot npm package and resolves resulting compilation and test failures.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill github-copilot-upgrader-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-copilot-upgrader
Source: https://github.com/Tyrizx/Tyrizx/tree/main/extensions/copilot/.agents/skills/github-copilot-upgrader
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill github-copilot-upgrader-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @github/copilot.

What problem does it solve? Upgrading the @github/copilot npm package in the vscode-copilot-chat project often introduces breaking API changes, type errors, and failing tests that require tedious manual analysis and fixes. ## Core Features & Use Cases - Guided Upgrade Workflow: Snapshots old type definitions, installs the latest @github/copilot package, and runs postinstall steps in a tracked TODO sequence. - API Diff Analysis: Compares old and new index.d.ts type definitions and documents breaking changes, new features, and deprecations in .build/upgrade-notes.md. - Compile-Fix-Test Loop: Iterates compilation (tsc --noEmit) and unit tests (npm run test:unit) until all errors and failures are resolved. - Use Case: When a new version of the GitHub Copilot SDK is released, run this Skill to perform the upgrade, identify API changes, fix type errors, and produce a summary report. ## Quick Start Upgrade the @github/copilot package to the latest version, fix any resulting type errors, and summarize the API changes.

Frequently Asked Questions about github-copilot-upgrader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade the @github/copilot npm package in vscode-copilot-chat?▼

Run npm install @github/copilot@latest followed by npm run postinstall, then compile with npm run compile and npx tsc --noEmit to surface type errors. Fix errors and run npm run test:unit until all tests pass.

How to find breaking changes after upgrading the GitHub Copilot SDK?▼

Snapshot node_modules/@github/copilot/sdk/index.d.ts before upgrading, then diff it against the new version's index.d.ts. Document new APIs, breaking changes, and removed deprecations in .build/upgrade-notes.md.

Why do tests fail after upgrading an npm dependency?▼

Test failures after an upgrade usually stem from changed APIs, altered behavior, or removed features in the new version. Analyze each failure to determine whether it reflects a legitimate upgrade issue or an outdated test, without changing code behavior just to pass tests.

Should integration tests run during a Copilot package upgrade?▼

No, this workflow explicitly excludes integration tests. It relies on TypeScript compilation checks and unit tests via npm run test:unit to validate the upgrade before summarizing changes.

What are the limitations of automated npm package upgrades?▼

Automated upgrades cannot resolve ambiguous design decisions or semantic behavior changes without human input. Complex breaking changes may require manual refactoring beyond mechanical type error fixes.