model-upgrade

Update default AI model references across configuration and documentation.

1|Updated Apr 10, 2024
One-click install
npx skills add https://github.com/EvaLok/schema-org-json-ld --skill model-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-upgrade
Source: https://github.com/EvaLok/schema-org-json-ld/tree/main/.claude/skills/model-upgrade
Command: npx skills add https://github.com/EvaLok/schema-org-json-ld --skill model-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear, step-by-step checklist to ensure all necessary code and documentation updates are made when changing the default AI model used by the Copilot coding agent.

Core Features & Use Cases

  • Consistent Model Updates: Ensures all references to the default model are updated across configuration files, system prompts, and documentation.
  • Reduces Errors: Minimizes the risk of inconsistencies that can arise from manual, scattered updates.
  • Use Case: When upgrading from gpt-5.3-codex to gpt-5.4, use this Skill to systematically update the default_model in tools/config.json, update model examples in .github/workflows/orchestrator-prompt.md, and verify the changes with cargo test.

Quick Start

Follow the checklist in this skill to update the default Copilot coding agent model.

Frequently Asked Questions about model-upgrade

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

FAQPage Schema
How do I update the default AI model for a Copilot coding agent?

To update the default AI model, systematically modify the `default_model` in `tools/config.json` and update model examples in `.github/workflows/orchestrator-prompt.md` to ensure configuration consistency.

What files need to be changed when upgrading an AI model version?

When upgrading an AI model version, you must update references in `tools/config.json` and `.github/workflows/orchestrator-prompt.md` to maintain consistency across configuration, system prompts, and documentation.

How do I verify AI model version changes in a coding agent configuration?

You verify AI model version changes by executing Rust tests using `cargo test` to ensure the configuration updates in `tools/config.json` and system prompts do not break existing functionality.

Why do configuration inconsistencies happen during a version upgrade?

Configuration inconsistencies happen during a version upgrade when manual, scattered updates miss references in system prompts or documentation, which a step-by-step checklist prevents by targeting specific files.

Can I use this checklist approach for updating any AI model in a coding agent?

Yes, you can use this checklist approach for updating any AI model in a Copilot coding agent, as it systematically targets configuration files, system prompts, and documentation regardless of the specific model version.