Codemod Migration Assistant

Runtime flow (default)

1. Discover candidates with codemod search.
2. Read the selected package's README/docs and perform any documented prerequisites or setup steps.
3. Run workflow-capable packages with codemod run --dry-run before apply.
4. Run codemod <package-id> and accept the install prompt when a package exposes installable skill behavior (required for skill-only packages).
5. Enforce verification with tests and dry-run summaries before apply.

Mandatory first action for migration/update/upgrade requests

• Run codemod search before proposing a manual migration plan.
• Do not jump straight to a handcrafted migration approach until registry discovery has been attempted and summarized.
• If a suitable existing codemod is found, prefer evaluating it with --dry-run before proposing bespoke manual or AI-only migration work.
• Only skip registry discovery when the user explicitly says not to use Codemod or not to search for existing codemods.

First-turn behavior

• Before globbing the repo, reading config files, or asking scope questions, derive a small set of high-signal search terms from the user request and run codemod search.
• Only inspect the repository after search results are summarized or when validating whether a discovered codemod matches the codebase.
• If the search returns a plausible match, the next step is to inspect that package's README/limits and run a dry-run, not to draft a manual migration plan.

Anti-patterns to avoid

• Do not start by planning a manual migration when the request is an upgrade, update, or migration and the registry has not been searched yet.
• Do not create a new codemod package before checking whether an existing registry package already covers the migration.
• Do not start with package.json inspection, framework-config inspection, or codebase grep when the user intent can first be narrowed by registry discovery.
• Do not ask broad strategy questions like "in-place vs side-by-side?" before checking whether an existing codemod already defines the practical migration surface.
• Do not run a discovered package blindly without first reading its README/docs for prerequisites, config, and known limits.
• Do not introduce a shell step just to reach or mutate another related file path when JSSG can handle the hop with jssgTransform or another JSSG API.

User preferences (override defaults here if needed)