1. Map what remains
Gilfoyle inventories the code still on the old pattern, the tests that cover it and the places where old and new must coexist. You agree the order, the slice size and what counts as done.
Run large code migrations
Give Gilfoyle a code migration, such as a new framework, API or router, and get it moved forward in small, tested pull requests your team can review.
migrations
Example brief · Hypothetical workflow
Your brief
We’re moving our API handlers to the new router. Continue the migration one module at a time, with tests, and keep both routers working until we switch.
GilfoyleAPP
I’ll map what is left, agree an order with you and migrate one reviewable slice at a time.
See example output ↓How Gilfoyle handles it.
Starts: When you hand over a migration plan or ask Gilfoyle to continue one already under way.
2. Migrate one slice at a time
With connected Claude Code or Codex and GitHub, each slice moves one module or area, keeps both paths working where the plan requires and runs the tests that cover that area.
3. Keep progress visible
Every draft PR states what moved, what remains and anything that needs a decision, and a tracking list shows progress across slices. Your reviewers merge each step; the final switch-over is your call.
Progress you can review in pieces.
Use this for changes that span many files or modules. For a single package version bump, upgrading dependencies safely is the lighter workflow.
Hypothetical finished result
Example output
Router migration progress update
Hypothetical: a service is part-way through moving its handlers to a new router.
- This slice
- Draft PR 4 of the plan moves the billing handlers. Route names, middleware order and error responses match the old handlers, and a compatibility test calls each route through both routers.
- Remaining
- Seven modules are still on the old router. Two use a custom auth middleware with no direct equivalent, so the update sets out two options instead of guessing.
- Checks
- Unit and route tests for billing pass. The full end-to-end suite could not run in this environment and is listed for the reviewer.
The apps this job needs.
Connect the accounts and actions for your workflow. Start in Artie or add your Artisan to Slack; access stays within your account permissions.
Explore apps- GitHub
- Connect the repository and allow branches and pull requests. Share the migration plan or tracking issue.
- Claude Code or Codex
- Connect the coding tool and provide an environment where the affected build and tests can run.
- Linear (optional)
- Connect the project if you track migration slices as issues.
Questions about this workflow
Will Gilfoyle open one huge PR?
No. The migration moves in slices sized for review, with old and new paths side by side where your plan needs them.
Who decides the final switch-over?
Your team. Gilfoyle prepares the remaining steps and checks; removing the old path is a reviewed decision.
What about code with no clean equivalent?
It is called out with options and trade-offs for a decision rather than forced into the new pattern.