dojo-migrate

Name: dojo-migrate
Availability: InStock
Author: Kepler22bee

Inspect, build, test, and execute profile-specific migrations for deployed Dojo worlds.

Updated Aug 27, 2026

Search Tags:#migration #migrate #schema-migration #dojo #sozo #starknet #world-migration

Ready to run

npx skills add https://github.com/Kepler22bee/House-of-Stark --skill dojo-migrate-kepler22bee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dojo-migrate
Source: https://github.com/Kepler22bee/House-of-Stark/tree/main/contracts/.agents/skills/dojo-migrate
Command: npx skills add https://github.com/Kepler22bee/House-of-Stark --skill dojo-migrate-kepler22bee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage breaking changes and version upgrades for deployed Dojo worlds by providing a structured migration workflow that reduces data loss, deployment errors, and downtime.

Core Features & Use Cases

Inspect and analyze world diffs to identify new or modified models and systems and detect potential breaking changes.
Build and validate changes locally with sozo build and sozo test before attempting migration.
Execute migrations with profile support and provide safe strategies for additive changes, parallel models, or full data migrations for breaking changes.
Use Case: Upgrade a live game from Dojo 1.7.x to 1.8.0 while preserving player data by inspecting changes, testing locally on Katana, and running a staged migration with a data migration system.

Quick Start

Migrate my deployed Dojo world to the target Dojo version by inspecting changes, running build and tests, and executing a profile-specific migrate while preserving data integrity.

Frequently Asked Questions about dojo-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a deployed Dojo world to a new version without losing data?▼

To migrate a deployed Dojo world safely, inspect world diffs for breaking changes, validate locally with sozo build and test, and execute a profile-specific migration using strategies like parallel models or data migration systems to preserve data integrity.

When do I need to use a parallel model strategy for Dojo schema migration?▼

A parallel model strategy is needed for Dojo schema migration when you introduce breaking changes to models or systems, allowing you to maintain data integrity by migrating data to new structures without corrupting the existing live world.

Can I test Dojo world migrations locally before deploying to production?▼

Yes, you can test Dojo world migrations locally by running sozo build and sozo test on a local Katana devnet to validate changes and ensure the migration workflow functions correctly before executing it on production worlds.

What is the best way to handle breaking schema changes in a Starknet Dojo project?▼

The best way to handle breaking schema changes in a Starknet Dojo project is to inspect world diffs, validate modifications, and apply safe migration strategies such as additive changes, parallel models, or deploying a new world.

Does sozo migrate support different profiles for testnet and production worlds?▼

Yes, sozo migrate supports profile-specific execution, allowing you to configure and run migrations distinctly across local devnets, testnets, and production worlds to manage deployment workflows safely.