agentsclimarketplace

Codebase migration batches

Skill yeaight7/agent-powerups/skills/codebase-migration-batches

Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more

Install
npx -y skills add yeaight7/agent-powerups --skill codebase-migration-batches

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a wide refactor or migration is too large to ship as one change — API renames across many files, framework or config migrations, or mechanical codemod-backed refactors that need reviewable batches.

SKILL.md

2.3 KB, as published. Nobody here has run it

Codebase Migration Batches

Use this skill for broad, repetitive refactors that should move in slices.

When to Use

  • API renames across many files
  • Framework or config migrations
  • Mechanical refactors backed by codemods or search/replace rules
  • Any change where "all at once" would be too large to review safely

Core Rules

  • Define the transform precisely before editing files
  • Keep one migration theme per batch
  • Prefer deterministic codemods over manual repetition
  • Maintain a batch ledger so already-migrated files are not touched twice
  • Validate each batch before moving to the next
  • No auto-commit, auto-push, or auto-PR

Workflow

  1. Define the migration

    • What changes
    • What does not change
    • How success is measured

  2. Measure the blast radius

    • Count affected files
    • Sample representative files
    • Identify edge cases before the first codemod pass

  3. Choose batch size

    • Small enough to review and debug
    • Large enough to make visible progress

  4. Run the transform

    • Prefer AST-aware tools when syntax matters
    • Use plain search/replace only for truly mechanical edits
    • Keep any helper scripts under versioned project control if they are reused

  5. Verify the batch

    • Run targeted tests first
    • Run broader validation when the batch changes shared primitives
    • Track residual manual fixes separately from the codemod logic

  6. Advance or stop

    • Continue if the batch is stable
    • Shrink the batch if review or validation gets noisy
    • Stop and redesign the transform if repeated manual cleanup dominates

Batch Ledger

Track at least:

Batch ID
Files included
Transform rule
Validation run
Known exceptions

Verification

  • The transform was defined precisely — what changes, what does not — before the first file edit
  • Each batch held one migration theme and passed validation before the next began
  • The batch ledger records files, transform rule, validation run, and exceptions for every batch
  • No already-migrated file was touched twice; no auto-commit, auto-push, or auto-PR occurred

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.