Works with the AI tools you already use
Dependency Upgrade Planner Pro
Professional dependency upgrade planning with risk scoring, usage mapping, and rollback strategies.
$5
Dependency Upgrade Planner Pro
Example session with this skill installed
I need to upgrade 'axios' from 0.21.1 to 1.6.0 in my Node.js project. Here is my package.json and the changelog link. Give me a risk assessment and an upgrade plan.
- Read your context and instructions
- Compiled the dependency upgrade planner
- Generated the document
I have analyzed the upgrade from
axios 0.21.1 to
1.6.0. This is a major version jump involving significant internal refactoring and API changes.
Upgrade Assessment: axios
| Metric | Value |
|---|---|
| Change Type | Major |
| Package Manager | npm |
| Initial Risk | High |
Risk Scoring
- Version Jump: 3/3 (Major)
- Breaking-Change Exposure: 3/3 (Multiple breaking changes in 1.x)
- API Surface: 2/3 (Used for all external API communication)
- Total Score: 14/21 (High Risk)
Changelog Review
| Change | Version | Relevance | Risk | Required Action |
|---|---|---|---|---|
| ESM Support | 1.0.0 | High | Med | Verify build tool compatibility with ESM modules. |
| Browser env removal | 1.0.0 | High | High | If running in Node, check process polyfills. |
| Response schema | 1.0.0 | High | Med | Audit data access on response.data. |
Usage Surface Analysis
- Imports: Found in
src/services/api.jsandsrc/hooks/useFetch.js. - Config: Custom instances created with
axios.create(). - Interceptors: Global request/response interceptors identified.
Upgrade Plan
- Baseline: Run current Vitest suite and record pass rates.
- Preparation: Audit interceptor logic for compatibility with the new internal
AxiosHeadersclass. - Upgrade: Execute
npm install axios@1.6.0. - Verification: Run targeted tests on
src/services/api.js. Check forTypeErrorin response handling. - Staging: Deploy to staging environment; monitor for 4xx/5xx spikes caused by header formatting changes.
Rollback Path
- Trigger: Any failed build or
AxiosErrorduring smoke tests. - Action:
npm install axios@0.21.1. - Verification: Ensure
package-lock.jsonreverts to previous hash.
Next steps
- Review the
AxiosHeadersmigration guide for custom interceptors. - Run the build command to check for ESM/CommonJS resolution conflicts.
- Update unit tests that mock the axios internal state.
dependency-upgrade-planner-pro.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Dependency upgrades are often treated as simple version bumps, leading to broken builds, runtime regressions, and production outages. Developers lack the time to manually audit changelogs, map API usage, and plan rollback strategies for every library update.
What it does
- Analyzes
package.json,requirements.txt, and lockfiles to detect version jumps and transitive dependency shifts. - Maps project source code to dependency APIs to identify specific breaking-change exposure.
- Calculates a multi-dimensional risk score based on version jump, API surface, and production criticality.
- Generates a phased implementation plan including targeted test hints, migration tasks, and rollback triggers.
Frameworks & tools
Compatible with Node.js (npm, yarn, pnpm), Python (pip, poetry), Go, Rust (Cargo), Ruby (Bundler), PHP (Composer), and Java (Maven, Gradle).
Why this beats prompting it yourself
General LLMs often hallucinate changelog details or assume semantic versioning is foolproof. This skill enforces a strict engineering workflow that separates known facts from assumptions and requires evidence for every compatibility claim.
Use cases
- Planning major framework migrations with high breaking-change risks.
- Auditing security patches to ensure fix compatibility with existing code.
- Generating PR descriptions that include verifiable test plans and rollback paths.
- Identifying coordinated upgrade requirements across microservices or monorepos.
Known limitations
Cannot execute file changes or run tests directly. Requires user-provided changelogs or release notes if they are not publicly accessible to the agent environment.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 6 days ago
- Passed all security checks, Safe to install