More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Framework Migration Architect

    1

    You're staring at a Next.js 13 → 14 upgrade, a Django 3.2 → 4.2 jump, or an Express → Fastify rewrite.

    Free

    3 usesSecurity scanned
    framework-migration-architect

    framework-migration-architect

    Example session with this skill installed

    "We need to migrate our Django 3.2 project to Django 4.2. It's a 12-module monolith with about 200 URLs and 15 custom middleware."

    • Read your context and instructions
    • Compiled the framework-migration-architect

    COMPATIBILITY REPORT — Django 3.2 → 4.2
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Files affected: 34
    Total instances: 67

    BLOCKING (must fix before upgrade):
    [CRITICAL] 12 files use django.conf.urls.url() — removed in 4.0
    [CRITICAL] 3 files use force_text() — removed in 4.0
    [CRITICAL] 1 file sets USE_L10N = False — setting removed in 4.0

    ADVISORY (should fix, won't crash):
    [HIGH] 8 files use deprecated PASSWORD_HASHERS config key
    [MEDIUM] 5 middleware classes inherit from old-style middleware

    PHASED PLAN
    Phase 0 (Prep): Update requirements.txt, run python -m django check
    Phase 1 (Non-breaking): Add django.urls.path() imports alongside old url()
    Phase 2 (Breaking): Replace url() → re_path(), force_text() → force_str()
    Phase 3 (Verify): Run full test suite, check deprecation warnings
    Phase 4 (Cleanup): Remove compat imports, update docs

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

    About this skill

    The Problem

    You're staring at a Next.js 13 → 14 upgrade, a Django 3.2 → 4.2 jump, or an Express → Fastify rewrite. The official migration guide has 40+ breaking changes. You don't know which ones actually affect your codebase. You start converting files, tests break in unrelated modules, and by Sunday night you're further behind than when you started. The agent you asked to help regenerates entire files, misses edge cases, and can't tell you which third-party packages will break before you discover it in production.

    What You Get

    • Migration readiness assessment that scans your entire codebase for deprecated APIs, removed features, and changed signatures — producing a compatibility report with severity ratings (blocking vs. advisory) and file-level impact counts
    • Phased transformation plan that orders changes by dependency graph — preparation, non-breaking changes, breaking changes, verification, and cleanup — so each phase can be tested and committed independently
    • Code transformation patterns with before/after examples for your specific framework pair (Pages → App Router, class → hooks, url() → path(), Express → Fastify, etc.) that handle the actual syntax changes, not abstract advice
    • Third-party compatibility map that flags packages in your dependency tree that may not support the target version, with recommended replacements or workarounds
    • Rollback instructions per phase — exact git commands, config reversions, and data migration rollback steps for every stage of the migration
    • Post-migration verification checklist covering unit tests, integration tests, type checking, linting, build success, runtime behavior, deprecated API cleanup, and performance baseline comparison

    Why This Beats Prompting It Yourself

    When you ask a generic agent to "upgrade Next.js 14," it starts rewriting files without mapping the full scope of changes. It misses config file format changes, third-party package incompatibilities, and subtle behavioral shifts in new APIs. The result: a half-migrated codebase where half the tests pass and the other half fail for reasons you can't trace. This skill forces a readiness assessment before any code is touched — the #1 failure mode in migrations is starting to transform code before understanding the full blast radius.

    Example Session

    You: "We need to migrate our Django 3.2 project to Django 4.2. It's a 12-module monolith with about 200 URLs and 15 custom middleware."

    Agent output:

    COMPATIBILITY REPORT — Django 3.2 → 4.2
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Files affected: 34
    Total instances: 67
    
    BLOCKING (must fix before upgrade):
      [CRITICAL] 12 files use django.conf.urls.url() — removed in 4.0
      [CRITICAL] 3 files use force_text() — removed in 4.0
      [CRITICAL] 1 file sets USE_L10N = False — setting removed in 4.0
    
    ADVISORY (should fix, won't crash):
      [HIGH] 8 files use deprecated PASSWORD_HASHERS config key
      [MEDIUM] 5 middleware classes inherit from old-style middleware
    
    PHASED PLAN:
      Phase 0 (Prep): Update requirements.txt, run `python -m django check`
      Phase 1 (Non-breaking): Add django.urls.path() imports alongside old url()
      Phase 2 (Breaking): Replace url() → re_path(), force_text() → force_str()
      Phase 3 (Verify): Run full test suite, check deprecation warnings
      Phase 4 (Cleanup): Remove compat imports, update docs
    

    Use Cases

    • Upgrading framework major versions (Next.js 13→14, Django 3→4, React 18→19, Vue 2→3)
    • Architectural migrations (Pages Router → App Router, class components → hooks, Express → Fastify)
    • Python version upgrades (2→3, 3.8→3.12 type hint modernization)
    • Spring Boot version jumps with deprecated API removal
    • Angular major version upgrades with RxJS migration

    Known Limitations

    Automated codemods (jscodeshift, libCST, 2to3) are powerful but can produce incorrect transformations for edge cases — always review codemod output manually. The skill does not execute migrations autonomously; it produces plans and patterns that a human or agent applies phase by phase with verification between each step.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    Automated codemods (jscodeshift, libCST, 2to3) are powerful but can produce incorrect transformations for edge cases — always review codemod output manually. The skill does not execute migrations autonomously; it produces plans and patterns that a human or agent applies phase by phase with verification between each step.

    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 buying a skill.

    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

    3 uses

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 5 months ago

    • Free with an Agensi account

    Software
    Python

    Permissions

    Terminal / Shell
    Network Access

    Allowed Hosts

    api.example.com
    Listed5 months ago

    What's inside

    Frequently Asked Questions

    The skill provides a specialized four-phase methodology—Assessment, Planning, Transformation, and Verification—that forces the agent to follow official migration paths rather than relying on general training data.

    The Framework Migration Architect is designed to work with any LLM-powered agent that has local or repository-level file access via its native environment.

    While the core methodology is language-agnostic, the skill includes optimized patterns for high-demand transitions like Next.js App Router migrations, React Hook conversions, and major Python version upgrades.

    You receive the comprehensive migration engine logic and a set of structured system instructions that transform your agent into a Senior Tooling Engineer.

    No, the skill prioritizes a phased approach that allows for incremental commits and testing, ensuring your project remains functional throughout the entire modernization process.

    Yes, this skill is specifically engineered to analyze your existing dependency tree to catch deprecated APIs and breaking changes before the migration begins.

    New in Code Quality & Review

    Free