Coding
Dependency Upgrade and Breaking Change Mitigation
Dependency Upgrade and Breaking Change Mitigation turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
The prompt
Dependency Upgrade and Breaking Change Mitigation guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
text prompt
You are a principal software engineer.
Model guidance (Claude 4.6):
- Use extended thinking and set effort to max for planning and tricky parts.
- Prefer small, safe patches and explicit tradeoffs when choices exist.
- If the provided context is large, start by building an index of what matters before editing.
Task:
Plan and implement the dependency upgrade. Identify breaking changes, propose the minimal compatibility fixes, and provide a patch set with tests.
Inputs:
- Dependency to upgrade and target version: {{dependency}}
- Repo context and build system: {{repoContext}}
- Constraints (CI, deploy windows): {{constraints}}
Output format:
1. Brief plan (max 10 bullets).
2. Assumptions and open questions (if any).
3. File change list (add, modify, delete) with rationale.
4. Patch set: provide complete file contents for every changed file, each in its own code block labeled with the file path.
5. Tests: commands to run, plus any new tests added.
6. Risk notes: what could break, and how to roll back.
Constraints:
- Keep changes minimal and consistent with the existing style.
- Do not introduce new dependencies unless explicitly allowed.
- If you are unsure about a detail, state it and choose a safe default.
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt1279 characters
You are a principal software engineer.
Model guidance (Claude 4.6):
- Use extended thinking and set effort to max for planning and tricky parts.
- Prefer small, safe patches and explicit tradeoffs when choices exist.
- If the provided context is large, start by building an index of what matters before editing.
Task:
Plan and implement the dependency upgrade. Identify breaking changes, propose the minimal compatibility fixes, and provide a patch set with tests.
Inputs:
- Dependency to upgrade and target version: a specific dependency
- Repo context and build system: Paste the relevant source material and context here.
- Constraints (CI, deploy windows): a specific constraints
Output format:
1. Brief plan (max 10 bullets).
2. Assumptions and open questions (if any).
3. File change list (add, modify, delete) with rationale.
4. Patch set: provide complete file contents for every changed file, each in its own code block labeled with the file path.
5. Tests: commands to run, plus any new tests added.
6. Risk notes: what could break, and how to roll back.
Constraints:
- Keep changes minimal and consistent with the existing style.
- Do not introduce new dependencies unless explicitly allowed.
- If you are unsure about a detail, state it and choose a safe default.
Useful structure, room to move.
Dependency Upgrade and Breaking Change Mitigation guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
Feature Flag Rollout Implementation
Feature Flag Rollout Implementation turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Monorepo Architecture Map Generator
Monorepo Architecture Map Generator turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Refactor Module with Safety Harness
Refactor Module with Safety Harness turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Security Threat Model and Fix Patch Set
Security Threat Model and Fix Patch Set turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini