github-copilot-upgrader

Upgrades the @github/copilot npm package and fixes resulting type errors in vscode-copilot-chat.

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

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 are tedious to track down manually. This Skill automates the entire upgrade workflow with a structured TODO-driven process. ## Core Features & Use Cases - Type Definition Diffing: Snapshots the old sdk/index.d.ts before upgrading and documents API changes, new features, and breaking changes in .build/upgrade-notes.md. - Compile-Fix-Test Loop: Runs npm install, postinstall, compile, and tsc --noEmit, then iterates on fixing type errors and unit tests until everything passes. - Upgrade Summary: Produces a documented summary of code changes, test changes, and type definition differences. - Use Case: When a new version of @github/copilot is released, invoke this Skill to perform the upgrade, resolve all resulting compilation errors, and generate upgrade notes without manual diffing. ## Quick Start Upgrade the @github/copilot package to the latest version and fix any resulting type errors and test failures.

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. This Skill automates that full sequence including test runs and documentation.

How to detect breaking changes after upgrading an npm SDK package?▼

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

Why do TypeScript compilation errors appear after upgrading @github/copilot?▼

New package versions can rename, remove, or change exported types and function signatures in the SDK. Run npx tsc --noEmit --project tsconfig.json to list all type errors, then analyze each before fixing call sites.

Should I change test behavior to make tests pass after a package upgrade?▼

No. Analyze each failure to determine whether it stems from a legitimate upgrade issue or a problem in the test itself. Fix the underlying code or the test accordingly rather than altering behavior just to force a pass.

Does this upgrade workflow run integration tests?▼

No. The workflow explicitly skips integration tests and relies on unit tests via npm run test:unit, repeating the compile-fix-test loop until all unit tests pass.