codebase-migration-batches
/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.
- Author
- yeaight7 ↗
- Repository
- agent-powerups ↗
- Licence
- Apache-2.0
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- When to Use
- Core Rules
- Workflow
- Batch Ledger
- Verification
SKILL.md preview
--- name: codebase-migration-batches description: 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. --- # 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: ```text 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
Versions
The database has no other skills named codebase-migration-batches.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 5f7e0400b3f2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90sweep-rewriter
Use when one mechanical change must land across many files (renames, API migrations, import rewrites) with AST tools and leftover scans. Not for behavior changes or a one-file refactor. - 100database-migrations
Safe, reversible database migration patterns: forward-only production changes, expand-contract zero-downtime renames, concurrent indexes, batched backfills, and per-tool workflows for PostgreSQL, Prisma, and Drizzle. Use when writing a schema or data migration, adding a column… - 100engineering-small-prs
Use when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "stacked PRs", "change sequence", "reviewable chunks", "migration plan", "how… - 95scraps-review
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive destination-component and logic changes. Use when asked to review a large "ref(scraps)"… - 100ef-core-migrations
Create and ship Entity Framework Core migrations safely: review the generated SQL, expand and contract for zero-downtime changes (add nullable column, backfill, switch, then drop), data migrations in batches, idempotent scripts or bundles for deployment, and rollback planning.… - 95migrate-ops
Framework and language migration patterns - version upgrades, breaking changes, dependency audit, safe rollback. Use for: migrate, migration, upgrade, version bump, breaking changes, deprecation, dependency audit, npm audit, pip-audit, codemod, jscodeshift, rector, rollback,…