Skip to content
cccskills
FreePublished on GitHub

github-copilot-upgrader

Use this to update the Github Copilot CLI/SDK

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

You are an expert at upgrading the @github/copilot npm package in the vscode-copilot-chat project.

Upgrade Process

You must create a TODO list of all items that are to be completed. You MUST create a TODO markdown file before commencing any of the work. Update this file after each step is completed. Complete all TODO items in sequence without stopping to ask for confirmation, only stop if you encounter any ambiguous decision that requires user input. The TODO is your primary tracking mechanism. Before each step you MUST read the TODO to determine what to do next.

At a minimum your TODO must contain the following:

  1. Snapshot old type definitions
  2. Update the package
  3. Compare differences in type definitions and document them
  4. Compile,
  5. fix
  6. test
  7. Repease steps Compile, fix and tests until all tests are passing
  8. Run integration tests
  9. Repeate Compile, Fix, Test, until all tests are passing
  10. Create a summary

Note:

  • Do not run any integration test.

Follow these steps exactly:

1. Snapshot of old type definitions

Take a snapshot of node_modules/@github/copilot/sdk/index.d.ts to compare against after the upghttps://github.com/microsoft/vscode/issues/291457rade.

2. Update the package using command npm install @github/copilot@latest

After this you MSUT run npm run postinstall

3. Compare differences in type definitions

  • Use mode=background for comparing the files and when done, just let me know its done
  • This is what you need to do in the background task:
    • Analyze the differences between the old and new index.d.ts files to identify any API changes, new features, or breaking changes.
    • Document the changes in a clear and organized manner, create the documentation in in .build/upgrade-notes.md

4. Compile, fix and test

4.1 Compile

  • Run the following commands to identify any type errors caused by the upgrade:
  • You must perform a deep analysis of the compilation errors before attempting to resolve them.
  • Ensure there are no compilation errors before proceeding to run the tests.
npm run postinstall
npm run compile
npx tsc --noEmit --project tsconfig.json

4.2 Run Tests

  • Use the following command to run test
npm run test:unit
  • Do NOT change the behavour of the code just to make the tests pass. If the upgrade causes a test to fail, you must analyze the failure and determine if it is due to a legitimate issue caused by the upgrade or if it is a problem with the test itself.
  • Ensure all tests are passing before proceeding to the next step.

5. Summarize the changes

  • After successfully upgrading the @github/copilot package and ensuring that all tests are passing, you must create a summary of the changes that were made during the upgrade process.
  • Give a summary of the changes in the code base
  • Give a summary of the changes in the tests
  • Give a summary of the differenes in the type definitions between the old and new versions of the @github/copilot package.
    • Focus on the new API or features that were added, any breaking changes that were introduced, and any deprecated features that were removed.
  • Document the summary in a clear and organized manner, create the documentation in in .build/upgrade-notes.md

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

See all skills by jcasnellie69

Report a problem with this skill