github-copilot-upgrader

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

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

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 type changes, compilation 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 Documentation: Compares old and new index.d.ts type definitions and documents breaking changes, new APIs, and deprecations in .build/upgrade-notes.md. - Compile-Fix-Test Loop: Runs npm compile, tsc type checks, and unit tests repeatedly until all errors are resolved and tests pass. - Use Case: When a new version of the GitHub Copilot SDK is released, use this Skill to perform the upgrade, analyze type definition changes, fix resulting type errors, and produce a summary of all codebase and test modifications. ## Quick Start Upgrade the @github/copilot package to the latest version, fix any compilation errors, and document 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 safely?▼

Snapshot the existing node_modules/@github/copilot/sdk/index.d.ts file, then run npm install @github/copilot@latest followed by npm run postinstall. Compare the new type definitions against the snapshot to identify breaking changes before fixing code.

How to find breaking changes after updating an npm package?▼

Compare the old and new index.d.ts type definition files to identify API changes, new features, and removed deprecations. Then run npm run compile and npx tsc --noEmit to surface every type error caused by the upgrade.

Why do tests fail after upgrading the GitHub Copilot SDK?▼

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

Does this upgrade workflow run integration tests?▼

No, the workflow explicitly excludes integration tests even though they appear in the TODO list. It relies on npm run test:unit for verification, repeating the compile-fix-test cycle until all unit tests pass.

What are the limitations of automated npm package upgrades?▼

Automated upgrades cannot resolve ambiguous design decisions when APIs change fundamentally, and they only catch issues surfaced by the TypeScript compiler and unit tests. Runtime behavior not covered by tests may still require manual verification.