claude-opus-4-5-migration

Migrate Claude Sonnet 4.x and Opus 4.1 prompts to Opus 4.5 across platforms.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/stevessr/dotsfiles --skill claude-opus-4-5-migration-stevessr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-opus-4-5-migration
Source: https://github.com/stevessr/dotsfiles/tree/main/dot_claude/private_plugins/private_marketplaces/claude-code-plugins/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration
Command: npx skills add https://github.com/stevessr/dotsfiles --skill claude-opus-4-5-migration-stevessr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrates prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5, updating model strings and prompt behavior to align with Opus 4.5 differences.

Core Features & Use Cases

  • Cross-platform model-string updates: Identify and replace source model strings with their Opus 4.5 targets across Anthropic API, AWS Bedrock, Google Vertex AI, and Azure Foundry.
  • Beta header handling & effort parameter: Remove unsupported beta headers and apply the required effort parameter to optimize performance.
  • Change documentation & guidance: Generate a concise summary of all modifications and provide user-facing guidance for troubleshooting and follow-ups.

Quick Start

Run the migration tool against your codebase to update all Claude Sonnet 4.x or Opus 4.1 references to Opus 4.5.

Frequently Asked Questions about claude-opus-4-5-migration

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

FAQPage Schema
How do I migrate Claude code from Sonnet 4.5 or Opus 4.1 to Opus 4.5?

To migrate Claude code to Opus 4.5, update existing model strings across Anthropic API, AWS Bedrock, Google Vertex AI, and Azure Foundry. The migration also removes unsupported beta headers and applies the required effort parameter to optimize prompt behavior.

What changes are needed for Opus 4.5 API updates on AWS Bedrock and Google Vertex AI?

Opus 4.5 API updates require replacing source model strings with Opus 4.5 targets across AWS Bedrock and Google Vertex AI. Additionally, you must remove unsupported beta headers and add an effort parameter to align prompt behavior with the new model.

Can I use the Opus 4.5 migration tool for Haiku model variants?

No, you cannot use the Opus 4.5 migration tool for Haiku model variants. The tool explicitly detects and ensures Haiku variants are not migrated, focusing solely on upgrading Sonnet 4.0, Sonnet 4.5, and Opus 4.1 references.

What is the best way to automate model string replacement across multiple platforms?

The best way to automate model string replacement is running a cross-platform migration tool that detects, replaces, and documents changes across Anthropic API, AWS Bedrock, Google Vertex AI, and Azure Foundry, providing a concise summary of all modifications.

Do I need to adjust prompts when updating to Opus 4.5?

Yes, you need to adjust prompts when updating to Opus 4.5. The migration process updates prompt behavior to align with Opus 4.5 differences, including removing unsupported beta headers and applying the required effort parameter for optimized performance.