Skip to content
Skills Library
Programming · Conversion & formats

dev-migrate

/dev-migrate

Plan and run a move of part or all of a project to another language, framework, database or platform, step by step with behaviour kept the same and proven by tests. Use for "/raystack project migrate", "migrate this service to Rust", "move from Express to Go", "port this to TypeScript", "switch from MySQL to Postgres", "rewrite this part in another stack".

Repository
RayStack ↗
Licence
MIT
Last repository change
06.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Plan and run a move of part or all of a project to another language, framework, database or platform, step by step with behaviour kept the same and proven by tests. Use for "/raystack project migrate", "migrate this service to Rust", "move from Express to Go", "port this to TypeScript", "switch from MySQL to Postgres", "rewrite this part in another stack".

Triggers from the description

migrate this service to Rustmove from Express to Goport this to TypeScriptswitch from MySQL to Postgresrewrite this part in another stack
Original author description

Plan and run a move of part or all of a project to another language, framework, database or platform, step by step with behaviour kept the same and proven by tests. Use for "/raystack project migrate", "migrate this service to Rust", "move from Express to Go", "port this to TypeScript", "switch from MySQL to Postgres", "rewrite this part in another stack".

How it works

  1. 1. Ask what to move
  2. 2. Map what exists
  3. 3. Research the target
  4. 4. Write the migration spec
  5. 5. Plan and build
Original SKILL.md headings · 63 lines, 533 words
SKILL.md preview
---
name: dev-migrate
description: Plan and run a move of part or all of a project to another language, framework, database or platform, step by step with behaviour kept the same and proven by tests. Use for "/raystack project migrate", "migrate this service to Rust", "move from Express to Go", "port this to TypeScript", "switch from MySQL to Postgres", "rewrite this part in another stack".
---

# Dev migrate

This skill turns "move X to Y" into research, a migration spec and a plan that `dev-build`
runs. The rule throughout: the old code keeps working until the new code is proven to do the
same thing. Formats and question rules are in `../dev/references/dev-contract.md`.

## 1. Ask what to move

Read `DECISIONS.md`, `docs/` and the code first. Then ask, one question per call, only what
is not already clear:

1. **What part?** Offer the modules, services or layers you found, plus "the whole project".
2. **To what?** The target language, framework, database or platform.
3. **Why?** Speed, cost, hiring, safety, a dead dependency. The reason decides what to
   measure at the end.
4. **Limits:** downtime allowed, then deadline, then data that must not be lost or reshaped
   (skip data when the part has no store). Each is its own question; never one numbered list.
   After the last one, ask the deployment shape only if research leaves it open.

Log each answer as a `D-` row.

## 2. Map what exists

For the chosen part, list in `docs/tech-spec/migration-<part>.md` under `## Current`:
its entry points (routes, CLI, jobs, events), the data it reads and writes, its callers, its
external calls, its config and secrets by name only, and the tests that cover it. Code with
no test is marked: it needs a characterisation test before it moves.

## 3. Research the target

Run `dev-research` on the target: maturity, libraries for each thing the part does today,
how it is deployed, how it talks to the code that stays. One table row per gap ("no mature
library for X"). A gap with no answer is an `Open` row and may stop the migration; say so.

## 4. Write the migration spec

In the same file, add:

- `Serves:` at the top, listing the B-IDs below, so `dev-plan` finds the spec.
- `## Behaviours`: B-IDs (the next free numbers after the PRD's) saying the new part does
  what the old one does (same inputs, same outputs, same errors, same data), plus one per stated reason ("p95 under 50 ms").
- `## Approach`: strangler by default. The new part runs beside the old, behind a route,
  flag or queue switch; traffic moves in steps; the old part is deleted last. A big-bang
  cutover needs a `## Complexity` row.
- `## Data`: dual-write or one-time copy, how it is checked (row counts, checksums), and the
  rollback for each step.
- `## Parity tests`: the same test cases run against old and new; the switch moves only
  when both pass.
- `## Done when`: every caller uses the new part, the old code and its config are deleted,
  and the reason is measured.

Log the stack change as a `D-` row that supersedes the `## Stack` row it replaces, and
update that row in `docs/architecture/system-overview.md`.

## 5. Plan and build

Hand to `dev-plan`: one task per step (characterisation tests, new part skeleton, parity
for each entry point, switch, data move, delete old), each step shippable and reversible on
its own. After the user approves the plan, `dev-build` runs it.

Tell the user the spec path, the B-IDs, the steps, the open rows and any gap that blocks.

Versions

The database has no other skills named dev-migrate.

Database snapshot: 13.11.2026 · package version ef8d0b976c1a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90dev
    Entry point for the RayStack development flow. Use for "/dev", "/raystack new project", "/raystack project new", "/raystack project update", "/raystack project gaps", "/raystack project review", "/raystack project migrate", "/raystack project refactor", "start a new project",…
  • 90raystack
    Entry point for everything in RayStack. Use for "/raystack", "what can RayStack do", development work ("new project", "project new", "project update", "project gaps", "project review", "project migrate", "project refactor", "refactor this", "start a project", "write a PRD",…
  • 90dev-writing-migrations
    Use when a change touches a live Postgres/MySQL schema: migration-plan.md at G3, migration files at G7, expand → migrate → contract, real rollback.
  • 95port-to-rust
    Run a port into Rust without losing behaviour — define the parity contract, sequence the phases, migrate incrementally behind a stable boundary, and prove parity differentially. Use when moving, porting, rewriting, or migrating an existing codebase into Rust from any language,…
  • 85code-migration
    Run a large-scale language migration with the six-step process: create the map and the rules, stress-test the rules, translate everything, compile, run it, match behavior. Use when the user wants to migrate, port, or rewrite a codebase from one language to another ("migrate this…
  • 100migrate-lumen
    Migrates a Lumen application to Laravel (optionally with Octane) step by step, keeping the same routes and behavior, and verifying with tests and a request-by-request comparison. Use when asked to migrate, upgrade or port a Lumen app to Laravel or Laravel Octane.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.