Coding & Debugging Prompts
Dependency Upgrade Migration Planner
Plan a safe library, framework, or runtime upgrade by mapping breaking changes, compatibility risks, tests, and rollback steps.
FreeClaudeChatGPT
Best for
Engineering teams upgrading important dependencies without mixing migration risk with unnecessary code modernization.
Suitable LLM groups
FrontierReasoning
Prompt
You are a software modernization engineer who specializes in high-confidence dependency and framework upgrades.
Inputs:
1. Dependency or runtime and current-to-target versions: {{upgrade_target}}
2. Application architecture and usage patterns: {{application_context}}
3. Release notes, deprecations, and migration guidance: {{change_information}}
4. Test coverage, deployment process, and environments: {{delivery_context}}
5. Compatibility, downtime, and deadline constraints: {{constraints}}
Do the following:
1. Inventory the application's direct and transitive use of the dependency, including APIs, configuration, plugins, generated code, build tools, and runtime assumptions.
2. Convert relevant breaking changes and deprecations into a compatibility matrix that identifies affected components, evidence, required code changes, and unknowns needing experiments.
3. Design the smallest safe sequence of upgrade steps, separating mechanical changes from behavioral changes and avoiding unrelated refactors.
4. Define compile, unit, integration, contract, performance, security, and production-smoke tests, with special attention to changed defaults and silent behavior differences.
5. Produce a migration checklist, risk-ranked work plan, dependency-conflict strategy, staged rollout, observability checks, and rollback procedure. Cite supplied migration guidance and label any inferred change.How to use
- Provide current and target versions plus lockfiles.
- List custom extensions and unusual usage patterns.
- Attach official migration notes when possible.
- Keep unrelated refactoring out of the upgrade branch.
Example input
Upgrade: Django 3.2 to 5.0. Context: 14-service monorepo, custom authentication backend, Celery tasks, PostgreSQL, and 63 third-party packages. Change information: Python 3.10 minimum, removed APIs, timezone behavior updates, and storage configuration changes. Delivery: 78% unit coverage, staging environment, weekly releases, canary deployment. Constraints: no customer downtime, complete within eight weeks, and preserve existing API behavior.
Example output
The plan first upgrades Python and dependencies while keeping Django 3.2, then moves through Django 4.2 LTS before 5.0 to isolate failures. The matrix flags custom authentication, timezone comparisons, file storage settings, and incompatible plugins. It adds contract tests for public APIs, task serialization tests, timezone boundary cases, and canary metrics for 5xx rates and task failures. Each phase has a lockfile, reversible database policy, and rollback to the previous image.
Customization tips
- — Include transitive dependencies and build plugins.
- — Call out changed defaults, not only removed APIs.
- — Specify database migration reversibility.
- — Use canary metrics tied to known behavioral risks.
Tags
#dependency-upgrade#framework-migration#breaking-changes#compatibility-testing#technical-debt
FAQ
What is this prompt for?
It turns dependency release information into a staged, testable migration and rollback plan.
How should I customize it?
Provide exact versions, architecture, dependency manifests, custom integrations, migration notes, test coverage, and deployment constraints.
Are there any limitations?
It cannot discover every dynamic or undocumented dependency behavior without running the application and its test suite.
How is it different from a basic prompt?
It maps actual usage to breaking changes and separates mechanical migration, behavior validation, rollout evidence, and rollback.
Related Prompts
All Coding & Debugging prompts →Free
Legacy Code Explainer & Refactor Planner
Explains what an unfamiliar or legacy piece of code actually does, then proposes a safe, incremental refactor plan instead of a risky full rewrite.
ClaudeChatGPT
#legacy-code#refactoring#code-review
Free
Database Query Performance Investigator
Analyze a slow database query using execution evidence, data distribution, indexes, and workload constraints before recommending changes.
ClaudeChatGPT
#sql-performance#query-plan#database-indexing
Free
Edge Case & Test Case Generator
Analyzes a function or feature and generates a comprehensive list of edge cases and corresponding test cases, catching scenarios developers commonly miss.
ClaudeChatGPT
#testing#edge-cases#unit-tests
Related Skills
Code ImprovementFree
Dependency Upgrade and Compatibility Planner
Plan safe framework and dependency upgrades with compatibility analysis, migration steps, tests, rollout, and rollback.
ClaudeChatGPTCursor
#dependency upgrade#framework migration#compatibility
Code ImprovementFree
Code Refactor Advisor
Reviews a code snippet and returns a prioritized refactor plan — readability, structure, and performance issues, each with a concrete fix.
ClaudeChatGPTCursor
#code-review#refactoring#clean-code
Code ImprovementFree
Code Refactoring Planner
Analyze a codebase or module and produce a safe refactoring plan with risks, boundaries, tests, migration steps, and acceptance criteria.
ClaudeChatGPTCursor
#code refactoring#technical debt#software architecture
Related articles coming soon — visit the Learn hub.