Mechanical code migration
Grinds through the mechanical half of a version bump or API migration — the hundred call sites that all change the same way. It proves the transformation on a handful first and gets approval before the rest, because a wrong rule applied to two hundred files costs more than the migration. It works in reviewable batches, runs the suite between them, and stops the moment it goes red.
Published by Oasis Platform · Free to add
This one runs on your own machine and works with whatever you already have there — no accounts to connect up front.
Claude CodeIt lands in your Oasis
Framework Migration Runner is created in your workspace with its instructions and settings already filled in.
You connect its apps
Nothing to connect — it works with what is already on your machine.
You make it yours
Rewrite the instructions, swap the model, add files and skills. It is a starting point, not a lock-in.
Runs in your terminal on a repo you actually have checked out, and answers the questions a new engineer wastes a week on. It starts from the entry points and follows the real call path rather than guessing from directory names, because directory names lie and imports don't. You get the layout, the request path with file references, the conventions the code really follows, and which parts are risky to touch.
Oasis PlatformEngineeringFinds the code paths your suite never touches and writes tests that would genuinely catch a regression. Coverage gaps are ranked by blast radius, so money, auth and data writes outrank a well-covered utility missing one line. It matches your existing test style exactly and runs everything it writes — it never hands over a test it hasn't seen pass.
Oasis PlatformEngineeringReads the commits since your last tag and writes the changelog. Each user-visible change is translated into what it means for someone using the software, and internal refactors, dependency bumps and test-only changes are dropped. When a commit message is unclear it reads the diff rather than paraphrasing the subject line.
Oasis PlatformEngineeringGive it a failing test or a stack trace and it works the problem in your local checkout. It reproduces the failure first and reads outward from where it actually breaks — never starting from a theory, because a fix for a bug you never saw fail is a guess. It fixes the cause rather than the symptom, and hands back a minimal diff with the suite green.
Oasis PlatformEngineeringAdd it to your Oasis, connect its apps, and hand it the first task. Everything about it stays editable.
© 2026 Oasis, Inc.
Add to your Oasis