This source did not publish a separate summary. Review SKILL.md before using the skill.
SKILL.md
Codebase Migrate
Coordinate framework upgrades, API renames, config rewrites, and structural refactors across hundreds of files. Local edits are driven by the agent; the Composio CLI handles the surrounding ceremony: tracking issues, per-batch PRs, and CI verification.
Any "change 200 files the same way" task that needs to ship in reviewable slices.
Prereqs
curl -fsSL https://composio.dev/install | bash
composio login
composio link github # for PRs + CI status
composio link linear # or jira — for migration tracking
Local tools the agent will use directly: git, rg, jscodeshift/ts-morph/comby/ast-grep (language-appropriate), and your test runner.
Planning Phase
Define the transform precisely. Bad: "migrate to vitest." Good: "replace jest.mock with vi.mock, swap jest.fn() for vi.fn(), rename jest.config.js → vitest.config.ts using template X."
composio execute LINEAR_CREATE_ISSUE -d '{
"teamId":"TEAM_ID",
"title":"Migrate test runner: jest → vitest",
"description":"Batches of ~25 files. Checkpoint after each PR lands green."
}'
Execute in Reviewable Batches
Loop: pick N files → transform → test → PR → wait for green → merge → next batch.
# Batch helper: first 25 untouched files matching the pattern
BATCH=$(rg -l 'jest\.mock' | grep -v done.list | head -25)
echo "$BATCH" > batch.list
The agent runs the codemod on batch.list, then:
git checkout -b migrate/vitest-batch-03
xargs < batch.list codemod-runner # e.g. jscodeshift / ts-morph / comby
npm test -- --changed
git add -A && git commit -m "migrate(test): jest → vitest (batch 3)"
git push -u origin migrate/vitest-batch-03
composio execute GITHUB_CREATE_A_PULL_REQUEST -d '{
"owner":"acme","repo":"app",
"head":"migrate/vitest-batch-03","base":"main",
"title":"migrate(test): jest → vitest (batch 3)",
"body":"Part of LIN-482. 25 files. Codemod: `transforms/jest-to-vitest.ts`."
}'
One transform per PR. Never mix a rename with a format change.
Keep a done.list of files already migrated so the next batch skips them.
Run the full test suite on the last batch, even if per-batch PRs ran --changed.
Codemod first, hand-edit second. If the codemod misses 3 files, patch them manually and note it in the PR body.
Roll back per-batch, not globally. Each PR should revert cleanly.
Verification Loop
After each merge:
rg 'jest\.(mock|fn|spyOn)' | wc -l # should trend to 0
npm test # full suite
composio execute GITHUB_LIST_WORKFLOW_RUNS_FOR_A_REPOSITORY \
-d '{"owner":"acme","repo":"app","branch":"main","event":"push"}' \
| jq '.workflow_runs[0].conclusion'
Troubleshooting
Codemod regex catches too much → switch to AST-based tooling (ast-grep, ts-morph) for structural matches.
Tests pass locally, CI fails → pin Node/Python version parity; check .nvmrc / pyproject.toml.
PR too big to review → cut batch size in half; maintainers won't review 800-line diffs.
Conflicts between batches → rebase the open batch before merging the current one; never force-push merged batches.
