Skip to content

a5c-ai/babysitter / library/specializations/code-migration-modernization/skills/framework-compatibility-checker

framework-compatibility-checker

Verified

Check codebase compatibility with target framework versions and generate migration paths

FileKindSize
README.mdmarkdown1.5 KB
SKILL.mdskill md3.0 KB
# Framework Compatibility Checker Skill

## Overview

The Framework Compatibility Checker skill assesses codebase compatibility with target framework versions. It identifies breaking changes and recommends safe migration paths.

## Quick Start

### Prerequisites

- Current framework version info
- Target version requirements
- Codebase access

### Basic Usage

1. **Identify current state**
   ```bash
   # Check current versions
   npm list react
   ```

2. **Check compatibility**
   - Review upgrade guides
   - Scan for deprecated APIs
   - Identify breaking changes

3. **Plan migration**
   - Map upgrade path
   - Estimate effort
   - Plan testing

## Features

### Compatibility Analysis

| Check | Description | Output |
|-------|-------------|--------|
| API Deprecation | Deprecated method usage | Replacement map |
| Breaking Changes | Incompatible changes | Migration steps |
| Version Conflicts | Peer dependency issues | Resolution plan |
| Polyfill Needs | Missing features | Polyfill list |

### Supported Frameworks

- React (all major versions)
- Angular (upgrade guide integration)
- Vue (migration tools)
- Next.js (codemods)
- Spring Boot
- .NET Core/5/6/7/8

## Configuration

```json
{
  "currentVersion": "17.0.0",
  "targetVersion": "18.0.0",
  "framework": "react",
  "includeDeprecations": true,
  "checkDependencies": true
}
```

## Related Documentation

- [SKILL.md](./SKILL.md) - Full skill specification
- [React Upgrade Guide](https://react.dev/blog)
- [Angular Update Guide](https://update.angular.io/)
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall