code-migration

Plan and execute phased Android/Kotlin migrations from legacy to modern technologies.

23|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/kirich1409/krozov-ai-tools --skill code-migration-kirich1409
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-migration
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/developer-workflow-kotlin/skills/code-migration
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill code-migration-kirich1409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, phase-driven approach to migrating Android/Kotlin projects from legacy patterns and libraries to modern equivalents, ensuring safety and traceability.

Core Features & Use Cases

  • Phase-driven migration: Discover FROM/TO, snapshot current behavior, choose a strategy, and migrate in controlled, reviewable steps.
  • Incremental delivery: Break migrations into small, independently mergeable PRs with green baselines.
  • Strategy catalog: In-place, Parallel (Expand-Contract), Branch by Abstraction, and Feature-flagged Parallel, plus bridge extension patterns for API changes.
  • Guardrails and verification: Green snapshots, visual diffs, behavior specs, and regression checks before final integration.
  • Use Case: Migrate from RxJava to coroutines, replace AsyncTask with coroutines, or swap XML layouts to Compose with a safe, auditable path.

Quick Start

Confirm the FROM/TO with the user and initiate a Snapshot baseline before starting the migration.

Frequently Asked Questions about code-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely migrate legacy Android Kotlin code to modern equivalents?

Safely migrate legacy Android Kotlin code by applying a phase-driven approach: discover the FROM/TO technologies, snapshot current behavior, execute the migration in controlled steps, and verify with regression checks. This ensures traceability and compatibility.

What is the best way to migrate RxJava to coroutines in an Android project incrementally?

The best way to migrate RxJava to coroutines is through incremental delivery, breaking the migration into small, independently mergeable pull requests. Establish a green baseline snapshot first, then use strategies like Branch by Abstraction to maintain compatibility.

Which migration strategy should I use when replacing XML layouts with Compose?

When replacing XML layouts with Compose, use strategies like Parallel (Expand-Contract) or Feature-flagged Parallel migrations. These approaches allow isolated changes and bridge extension patterns for API changes, ensuring existing callers remain unaffected during the transition.

Can I use feature flags to control Android Kotlin migrations and maintain a green test baseline?

Yes, you can use feature flags to control Android Kotlin migrations. The Feature-flagged Parallel strategy respects risk controls by isolating changes, allowing you to maintain a green test baseline and verify behavior specs before final cutover integration.

What are the limitations of migrating AsyncTask to coroutines without a snapshot baseline?

Migrating AsyncTask to coroutines without a snapshot baseline risks breaking existing behavior. Without green snapshots and visual diffs, you lack the necessary guardrails to catch regressions or ensure compatibility with existing tests before applying the migration strategy.