Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Dependency Upgrade Planner Pro

    2

    Professional dependency upgrade planning with risk scoring, usage mapping, and rollback strategies.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Dependency Upgrade Planner Pro

    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

    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

    MetricValue
    Change TypeMajor
    Package Managernpm
    Initial RiskHigh

    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

    ChangeVersionRelevanceRiskRequired Action
    ESM Support1.0.0HighMedVerify build tool compatibility with ESM modules.
    Browser env removal1.0.0HighHighIf running in Node, check process polyfills.
    Response schema1.0.0HighMedAudit data access on response.data.

    Usage Surface Analysis

    • Imports: Found in src/services/api.js and src/hooks/useFetch.js.
    • Config: Custom instances created with axios.create().
    • Interceptors: Global request/response interceptors identified.

    Upgrade Plan

    1. Baseline: Run current Vitest suite and record pass rates.
    2. Preparation: Audit interceptor logic for compatibility with the new internal AxiosHeaders class.
    3. Upgrade: Execute npm install axios@1.6.0.
    4. Verification: Run targeted tests on src/services/api.js. Check for TypeError in response handling.
    5. Staging: Deploy to staging environment; monitor for 4xx/5xx spikes caused by header formatting changes.

    Rollback Path

    • Trigger: Any failed build or AxiosError during smoke tests.
    • Action: npm install axios@0.21.1.
    • Verification: Ensure package-lock.json reverts to previous hash.

    Next steps

    • Review the AxiosHeaders migration guide for custom interceptors.
    • Run the build command to check for ESM/CommonJS resolution conflicts.
    • Update unit tests that mock the axios internal state.

    Connects securely to your tools. The creator never sees your data.

    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.

    Requires manual input of changelogs if not accessible via tools. Does not perform automated code edits or deployments. Scope is limited to evidence provided in lockfiles and source code.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Unlike generic prompts, this skill performs an 'impact analysis' by mapping your specific source code to the dependency's API, identifying exactly which functions in your project are at risk of breaking.

    The skill is designed to work with any agent that has access to your project's file structure, including popular coding assistants and CLI-based AI agents.

    No, the planner operates in a 'read-only' capacity to ensure safety; it provides the migration steps, risk scores, and test plans, but you maintain full control over the final code execution.

    You receive the complete skill configuration, detailed documentation on the risk scoring methodology, and suggested system prompts for various package managers.

    The skill uses a multi-dimensional scoring system that evaluates the size of the version jump, the criticality of the affected API surface, and the history of transitive dependency shifts.

    While it supports major ecosystems like Node.js, Python, and Go out of the box, it can analyze any language as long as you provide the relevant manifest file and access to the project source code.

    New in LLM Ops