upgrade-config

Upgrade Copilot bootstrap configurations to the latest toolkit version.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/vndkubi/code-graph --skill upgrade-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-config
Source: https://github.com/vndkubi/code-graph/tree/main/.github/skills/upgrade-config
Command: npx skills add https://github.com/vndkubi/code-graph --skill upgrade-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade bootstrap configurations by migrating an existing Copilot setup to the latest toolkit version.

Core Features & Use Cases

  • Read the current bootstrap manifest and compare it to the target toolkit version.
  • Generate a migration plan that updates .github bootstrap files, manifests, and generated agents.
  • Apply planned changes and update the manifest to reflect the new toolkit version.

Quick Start

Execute the upgrade-config workflow in your repository to generate a migration plan and apply updates to bootstrap files.

Frequently Asked Questions about upgrade-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade my Copilot bootstrap configuration to a newer toolkit version?

To upgrade a Copilot bootstrap configuration, execute the automated workflow to read the existing .github/.bootstrap-manifest.json, generate a migration plan against the target toolkit version, and apply updates to the manifest and related bootstrap files.

What does a bootstrap manifest migration plan include when updating Copilot configurations?

A bootstrap manifest migration plan includes diffs comparing current toolkit capabilities against the target version, and the specific updates required for .github bootstrap files, the manifest itself, and generated Copilot agents to ensure alignment.

When do I need to migrate my Copilot bootstrap files to the latest toolkit version?

You need to migrate Copilot bootstrap files when integrating a newer toolkit version into an existing project to align the manifest, generated files, and bootstrap state with the updated capabilities and configurations.

Can I automate manifest and bootstrap state updates without manually diffing Copilot configurations?

Yes, the automated upgrade process reads the existing .github/.bootstrap-manifest.json, performs the diff against current toolkit capabilities automatically, and applies the planned updates to the manifest and related bootstrap files without manual intervention.

What are the limitations of automating Copilot configuration upgrades for existing projects?

The automated upgrade process requires an existing .github/.bootstrap-manifest.json file to function. It is designed for projects with an established Copilot bootstrap setup and cannot generate initial configurations for new projects lacking a manifest.