Automate LLM Model Migrations
Upgrading your codebase to a newer LLM model (e.g., GPT-4 to GPT-4o, or Claude 3 to 3.5) often breaks logic due to hardcoded version strings, deprecated API parameters, or legacy token limits. The Model Migration Checker is a specialized audit tool designed for developers who need to identify migration risks before they hit production errors.
What it does
This skill scans your repository (Python, JavaScript, TypeScript, and config files) to detect six critical categories of model coupling:
- Hardcoded Models: Specific version strings nested in API calls.
- Deprecated Parameters: Arguments no longer supported by modern provider SDKs.
- Context Assumptions: Legacy token limits or hardcoded context window sizes.
- Coupling: Rigid response-parsing logic or function-calling schemas that break with model output variations.
- Cost Constants: Hardcoded pricing data used for internal usage tracking.
Why use this skill
Unlike a generic AI prompt, this skill uses a structured heuristic engine to catch "silent failures" that a human or a standard LLM call might overlook. It provides a technical audit trail with specific rule IDs and severity levels, allowing you to systematically clear blockers before a model swap. It ensures your infrastructure is model-agnostic and resilient to future provider updates.