migration-compatibility_skill

This skill helps design and evaluate migration compatibility layers, adapters, and abstractions to ensure safe, incremental coexistence of old and new systems.

Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shotaiuchi/dotclaude --skill migration-compatibility

SKILL.md1.7 KB

Overview

This skill helps design compatibility layers and migration bridges to connect legacy and modern systems. It focuses on adapters, abstraction layers, coexistence strategies, and phased migration plans to reduce disruption. The output is a pragmatic checklist and a risk-rated report to guide implementation choices.

How this skill works

The skill inspects API differences, shared state, dependency versions, and runtime interactions to define adapters or shims. It maps call sites to version-agnostic abstractions, specifies incremental migration phases with rollback points, and evaluates coexistence risks. Finally it produces findings with risk ratings (Critical, High, Medium, Low) to prioritize work.

When to use it

When replacing core services but keeping parts of the legacy system running
When introducing new APIs that are incompatible with existing callers
When building an adapter, shim, or polyfill to avoid mass refactor
When planning phased, reversible migrations to minimize outage risk
When validating that multiple versions can run concurrently in production

Best practices

Define clear adapter interfaces that translate intent, not just signature
Isolate version-specific code behind small, testable abstractions
Design each migration phase to deliver a working system and a safe rollback path
Validate coexistence with integration tests covering shared-state and dependency conflicts
Measure adapter performance and ensure overhead stays within acceptable limits
Document safe stopping points and criteria for advancing phases

Example use cases

Create an adapter layer that translates legacy API payloads to the new API format with error mapping and retries
Design a version-agnostic service facade that hides divergent client libraries behind a single interface
Implement an incremental migration plan: feature flag, partial roll out, monitor, then shift traffic
Build shims to emulate deprecated behavior while new implementations are deployed
Run coexistence tests that simulate mixed-version traffic and check for state corruption

FAQ

Start by cataloging API differences, shared state points, and runtime dependencies; map all affected call sites to prioritize adapters.

How do I decide risk rating for a migration task?

Assess feasibility of translation, required effort, potential for data loss, and ability to roll back; use Critical/High/Medium/Low to communicate urgency and effort.