github-copilot-upgrader

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

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

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. - Type Definition Diffing: Compares old and new index.d.ts files in a background task and documents API changes, new features, and breaking changes in .build/upgrade-notes.md. - Compile-Fix-Test Loop: Iterates compilation, error analysis, and unit test runs until all tests pass, then produces a structured upgrade summary. - Use Case: When a new version of the GitHub Copilot SDK is released, use this Skill to perform the upgrade end-to-end and receive documented notes on every API change and code fix applied. ## Quick Start Upgrade the @github/copilot package to the latest version, fix any resulting compile errors and test failures, and document the API changes in .build/upgrade-notes.md.

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 detect breaking changes after upgrading an npm package?▼

Snapshot the old type definitions file (node_modules/@github/copilot/sdk/index.d.ts) before upgrading, then diff it against the new version. Document new APIs, breaking changes, and removed features in an upgrade notes file.

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

Test failures after an upgrade usually stem from changed APIs, renamed methods, or altered behavior in the new SDK version. Analyze each failure to determine whether it reflects a legitimate code issue or an outdated test expectation before changing anything.

Should I modify code behavior just to make tests pass after an upgrade?▼

No. Changing behavior solely to pass tests can mask real regressions introduced by the upgrade. Investigate each failure to determine whether the code or the test itself needs updating, and only fix the actual root cause.

Does this upgrade workflow run integration tests?▼

No. The workflow explicitly excludes integration tests and relies on TypeScript compilation checks and unit tests via npm run test:unit to validate the upgrade.