GitHub Copilot SDK Upgrade Assistant
Upgrade and validate @github/copilot in the VS Code Copilot Chat project.
The skill explicitly requires npm package installation, postinstall execution, compilation, and tests, creating external dependency and code-execution effects, but it does not define permission scope, data flow, sensitive-data handling, user confirmation, rollback, or version pinning. Repository MIT licensing and official provenance justify limited trust credit only.
The procedure covers snapshotting, installation, compilation, and unit testing, but directly contradicts itself by requiring integration tests and also forbidding all integration tests. It also contains spelling, numbering, and path-quality issues. Repository CI evidence exists, but does not reproduce this skill path, so the score remains very low.
The target scenario and main input—upgrading @github/copilot in the VS Code Copilot project—are reasonably clear, but applicability boundaries, failure conditions, environment requirements, and trigger exclusions are not stated. No Chinese-language support or mainland-China network reachability is documented.
The document is organized by upgrade phase and provides commands and an output-document location. However, it lacks prerequisites, version policy, changelog, maintenance ownership, update path, troubleshooting, and known limitations; the TODO requirements also contain missing numbering and a duplicated summary. MIT licensing and Microsoft attribution are supported by repository files.
On the happy path it may complete dependency upgrading, type-difference documentation, and testing. However, the integration-test contradiction, lack of recovery guidance, and absence of representative verified outputs or alternative approaches mean the final result may require substantial manual judgment.
The skill names concrete commands and target files, while the repository provides some GitHub Actions, dependency-locking, and test-code evidence as audit signals. Those materials do not cover the skill's key upgrade path, and this review is static only, so execution, outputs, and test success remain unverified.
- The integration-test instructions are contradictory; the user must resolve whether integration tests should run before execution.
- npm install @github/copilot@latest introduces an unpinned latest version without rollback or change-approval guidance.
- Credential handling, network requests, postinstall side effects, and recovery after failure are undocumented.
- No Chinese interaction, restricted-network adaptation, or fallback for unavailable npm/GitHub services is documented.
What does this skill do, and when should you use it?
This skill targets upgrades of the @github/copilot npm package in the vscode-copilot-chat project. It requires taking a snapshot of the old type definitions, installing the latest package, running postinstall, and comparing the before-and-after index.d.ts files. It then directs compilation, fixes, unit testing, and documentation of the upgrade. The SKILL.md lists an integration-test step but explicitly says not to run any integration test.
It requires creating and updating a TODO Markdown file as the primary upgrade tracker. It snapshots node_modules/@github/copilot/sdk/index.d.ts, runs npm install @github/copilot@latest, and then runs npm run postinstall. It requires comparing the old and new type definitions and documenting API changes, new features, breaking changes, or removals in .build/upgrade-notes.md. It also requires running npm run compile, npx tsc --noEmit --project tsconfig.json, and npm run test:unit; after failures, it calls for analysis and fixes, followed by a summary of code, test, and type-definition changes.
- A VS Code Copilot Chat maintainer needs to move @github/copilot to the latest version and follow a defined upgrade sequence.
- A TypeScript project needs to identify type errors caused by an npm package upgrade and compare index.d.ts changes.
- A developer needs to validate existing unit tests after a dependency update and record the results in .build/upgrade-notes.md.
- A team needs a persistent checklist covering upgrade tasks, type differences, compilation, and test results.
What are this skill's strengths and limitations?
- Covers package installation, postinstall, type-definition comparison, compilation, type checking, unit tests, and a final summary.
- Requires a TODO file to track each step and update it after completion.
- Requires analysis of compilation and test failures rather than changing code behavior merely to make tests pass.
- Has a focused scope: the @github/copilot npm package in the vscode-copilot-chat project.
- The source does not specify a standalone installation method, required Node.js version, or complete runtime environment.
- The SKILL.md contains wording and sequencing problems, including “Repease,” “Repeate,” and a missing item number 10.
- The checklist says to run integration tests, while a later note explicitly says not to run any integration test.
- It provides no detailed repair strategy, test-coverage description, or failure-handling policy beyond analysis and fixing.
- It depends on local file access, npm commands, and network access, but the source provides no cross-platform validation evidence.
How do you install this skill?
The repository README does not provide standalone installation instructions for this skill or specify which client directory should contain it. The file is located at extensions/copilot/.agents/skills/github-copilot-upgrader/SKILL.md. The README states that the overall VS Code Code - OSS repository is licensed under MIT, but it gives no separate installation command for this skill.
How do you use this skill?
In an Agent Skills client where the skill is configured, ask for an @github/copilot upgrade in the vscode-copilot-chat project, for example: “Upgrade @github/copilot to the latest version in vscode-copilot-chat, and record the type-definition differences, compilation results, and unit-test results as required by the skill.” The source does not document a specific trigger mechanism, working-directory setup, or client integration procedure.