What does the Framework Compatibility Checker do?

It analyzes code for deprecated APIs and breaking changes, maps current to target framework versions, and generates a recommended migration path along with risk assessment.

Which frameworks are supported?

Supports major frameworks via integrated guides and tools: Angular, React, Next.js, Spring, Vue, and .NET (e.g., Angular Update Guide, React Codemod, Next.js Upgrade, Spring Boot Migrator, Vue Migration Guide, .NET Upgrade Assistant).

What outputs are produced?

An Output Schema including analysisId, timestamp, current/target frameworks, a compatibility verdict, a migrationPath with steps and intermediate versions, and a risk assessment.

framework-compatibility-checker

npx machina-cli add skill a5c-ai/babysitter/framework-compatibility-checker --openclaw

Files (1)

SKILL.md

2.6 KB

Framework Compatibility Checker Skill

Checks codebase compatibility with target framework versions, identifies breaking changes, and recommends migration paths.

Purpose

Enable framework upgrade assessment for:

Deprecated API detection
Breaking change impact analysis
Compatibility matrix generation
Migration path recommendation
Risk assessment

Capabilities

1. Deprecated API Usage Detection

Find deprecated method calls
Identify removed APIs
Detect obsolete patterns
Map replacement APIs

2. Breaking Change Impact Analysis

Analyze upgrade changelogs
Match breaking changes to code
Estimate impact scope
Prioritize by severity

3. Compatibility Matrix Generation

Map current vs target versions
List compatible dependencies
Identify version conflicts
Generate upgrade paths

4. Migration Path Recommendation

Suggest incremental upgrades
Identify intermediate versions
Recommend safe upgrade order
Plan breaking change handling

5. Risk Assessment

Score upgrade difficulty
Identify high-risk areas
Estimate testing needs
Calculate timeline impact

Tool Integrations

Tool	Framework	Integration Method
Angular Update Guide	Angular	Web / API
React Codemod	React	CLI
Next.js Upgrade	Next.js	CLI
Spring Boot Migrator	Spring	CLI
Vue Migration Guide	Vue	Web / CLI
.NET Upgrade Assistant	.NET	CLI

Output Schema

{
  "analysisId": "string",
  "timestamp": "ISO8601",
  "current": {
    "framework": "string",
    "version": "string"
  },
  "target": {
    "framework": "string",
    "version": "string"
  },
  "compatibility": {
    "compatible": "boolean",
    "breakingChanges": [
      {
        "type": "string",
        "description": "string",
        "locations": [],
        "migration": "string",
        "effort": "string"
      }
    ],
    "deprecations": [],
    "removedApis": []
  },
  "migrationPath": {
    "steps": [],
    "intermediateVersions": [],
    "estimatedEffort": "string"
  },
  "risk": {
    "score": "number",
    "factors": []
  }
}

Integration with Migration Processes

framework-upgrade: Primary compatibility check
language-version-migration: Version analysis

Related Skills

codemod-executor: Automated fixes
dependency-updater: Dependency upgrades

Related Agents

framework-upgrade-specialist: Upgrade execution

Source

git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/specializations/code-migration-modernization/skills/framework-compatibility-checker/SKILL.md

View on GitHub

Overview

Checks codebase compatibility with target framework versions, identifies deprecated APIs and breaking changes, and plans migration paths. It builds a compatibility matrix, flags version conflicts, and suggests safe upgrade sequences. It also performs risk assessment to estimate effort and testing needs.

How This Skill Works

The checker scans the codebase to detect deprecated API usage, removed APIs, and obsolete patterns, correlating findings with upgrade changelogs. It maps current vs. target versions, generates a compatibility matrix, and outputs a migration path with intermediate versions and estimated effort.

When to Use It

Planning a major framework upgrade with potential breaking changes
Evaluating deprecated API usage before refactoring
Generating a compatibility matrix to surface version conflicts
Recommending incremental upgrade steps to minimize risk
Assessing upgrade risk and required testing effort

Quick Start

Step 1: Run analysis on the codebase against the target framework version
Step 2: Review the generated compatibility matrix and migration path
Step 3: Apply incremental upgrades and validate with tests

Best Practices

Define current and target versions clearly before analysis
Run deprecated API detection first to scope changes
Cross-check with official upgrade guides and changelogs
Prioritize safe intermediate versions for large upgrades
Incorporate testing scope and timelines into migration plan

Example Use Cases

Upgrade an Angular app from an older version to the latest using the Angular Update Guide
Migrate a React project with codemods to align with newer React versions
Move a Next.js app from an older major version to a newer one with CLI guidance
Migrate a Spring Boot project from 2.x to 3.x using a migration path
Upgrade a .NET application using the .NET Upgrade Assistant and plan tests

Frequently Asked Questions

Add this skill to your agents