Codebase migration batches

Skill yeaight7/agent-powerups/plugins/software-engineering/skills/codebase-migration-batches

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.From its SKILL.md

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.

SKILL.md

2.3 KB, 474 tokens by cl100k_base, 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

Define the migration
- What changes
- What does not change
- How success is measured
Measure the blast radius
- Count affected files
- Sample representative files
- Identify edge cases before the first codemod pass
Choose batch size
- Small enough to review and debug
- Large enough to make visible progress
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
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
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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most architecture codebase skills give in 474 tokens

Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06

Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
Document architecture decision recordsin 20 of 858, across 12 files
Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
Write HTML report to the system temp directoryin 17 of 858, across 14 files
Read product marketing context before asking questionsin 16 of 858, across 6 files
Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
Ensure every page has at least one internal linkin 15 of 858, across 5 files
Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
Enforce lowercase URLs with hyphensin 15 of 858, across 5 files

Said here and by no other author read

define the transform precisely before editing
keep one migration theme per batch
prefer deterministic codemods over manual repetition
maintain a batch ledger
run targeted tests before broader validation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.