dojo-migrate

Coordinate Dojo world migrations, upgrades, and breaking-change handling via the Dojo toolchain.

53|92|Updated Mar 28, 2023
One-click install
npx skills add https://github.com/dojoengine/book --skill dojo-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dojo-migrate
Source: https://github.com/dojoengine/book/tree/main/skills/dojo-migrate
Command: npx skills add https://github.com/dojoengine/book --skill dojo-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing migrations and upgrades for deployed Dojo worlds, including handling breaking changes and version upgrades, to keep systems in sync with evolving schemas and contracts.

Core Features & Use Cases

  • Analyze migration diffs and plan safe, incremental updates
  • Execute migrations and manage breaking changes across models and systems
  • Upgrade Dojo versions and coordinate deployment workflows

Quick Start

Start by inspecting the current world state, then build, test, and migrate deployed worlds.

  • Update existing world: "Migrate my changes to the deployed world"
  • Version upgrade: "Upgrade my project to Dojo v1.8.0"

Frequently Asked Questions about dojo-migrate

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

FAQPage Schema
How do I migrate changes to a deployed Dojo world?

To migrate changes to a deployed Dojo world, inspect the current world state, then build, test, and execute migrations via the Dojo toolchain to keep systems in sync with evolving schemas.

How do I upgrade my project to a new Dojo version?

Upgrading to a new Dojo version involves coordinating the deployment workflow to manage version upgrades and handle breaking changes across models and systems automatically.

What is the best way to handle breaking changes in Dojo models?

Handling breaking changes in Dojo models requires analyzing migration diffs to plan safe, incremental updates, then executing the migration to manage schema changes across systems.

When do I need to run a Dojo world migration?

A Dojo world migration is needed when updating deployed worlds, handling version upgrades, or managing breaking changes to keep systems in sync with evolving schemas and contracts.

Can I automate schema changes across Dojo models and systems?

Yes, schema changes across Dojo models and systems can be automated through a structured workflow that coordinates inspection, build, test, and deployment steps via the Dojo toolchain.

Why does upgrading Dojo versions require coordinating deployment workflows?

Upgrading Dojo versions requires coordinating deployment workflows because version upgrades introduce breaking changes that must be managed across models and systems to maintain schema synchronization.