migrating-rule-packs

Rule-pack migrations coordinate mechanical code changes by applying deterministic transformations to target files using parallel git worktrees. This approach enables autonomous per-file workflows with isolated branches for deterministic, parallelizable transformations across many files.

Parallel worktree workflows isolate mechanical code transformations by creating an autonomous per-file git branch for each target file. They run a built-in build, check, and test loop with retry logic before automatically creating individual pull requests for every migrated file.

Yes, rule packs are designed for deterministic, mechanical migrations such as moving from zod to typebox or lifting import paths. They package transformation rules applied repeatedly across many target files in parallel using isolated git worktrees.

PR review feedback can be rewritten into migration rules using a built-in feedback loop. This mechanism captures reviewer comments and converts them into rule-pack rules, enabling continuous improvement for subsequent automated code transformations.

To start a mechanical code migration, survey the target files, land a reference PR, and implement a parallel worktree workflow. This establishes a repeatable pattern for migrating each file autonomously with automated validation and feedback.

Parallel worktree migrations should be avoided for non-deterministic or highly interdependent code changes. This approach requires transformations to be mechanical and parallelizable, making it unsuitable for complex refactoring lacking isolated, per-file boundaries.