skills.rest
stoodder
stoodderCOMMUNITY
Explore all skills by this author ā†’
GitHub

migrate

Execute deterministic migrations for Materia projects using release ledger compatibility.

1|Updated Jul 5, 2026
Search Tags:#version control#compatibility#migration#project upgrade#materia
One-click install
npx skills add https://github.com/stoodder/materia --skill migrate-stoodder
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/stoodder/materia/tree/main/plugins/materia/skills/migrate
Command: npx skills add https://github.com/stoodder/materia --skill migrate-stoodder

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of upgrading a Materia-installed project, ensuring compatibility and reducing manual intervention.

Core Features & Use Cases

  • Project Upgrade Planning: Analyze the current and target project schemas, identifying necessary migrations.
  • Safe Migration Execution: Apply only safe, deterministic, and idempotent migrations.
  • Change Acknowledgment: Record changes identified by /materia:doctor for future consideration.
  • Use Case: If /materia:doctor reports a stale or legacy project, use this Skill to plan the necessary upgrades and apply them safely.

Quick Start

Run the migrate skill to plan the upgrade for the current project directory.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I plan a project upgrade for a legacy Materia repository?ā–¼

To plan a project upgrade, execute the migration engine with the planning flag to compare your current project state against a target schema. This analyzes the release ledger to identify necessary compatibility migrations.

What is the safest way to apply version control migrations to a Materia project?ā–¼

The safest way to apply migrations is using the deterministic migration engine, which only executes safe, idempotent operations based on a target schema. This ensures compatibility and reduces manual intervention during project upgrades.

How do I acknowledge changes identified by a project doctor scan for future migration?ā–¼

You can acknowledge changes by running the migration engine with the specific acknowledgment flag. This records changes identified by the doctor's available adoptions for future consideration and safe execution.

Do I need to provide a project root directory to execute a Materia migration?ā–¼

Yes, you must provide the project root directory and specific flags to execute the migration engine. The engine requires these parameters to accurately compare release ledger compatibility and apply safe, deterministic migrations.

When should I use a deterministic migration engine for project upgrades?ā–¼

You should use a deterministic migration engine when a doctor scan reports a stale or legacy Materia-installed project. It ensures safe, idempotent migrations that maintain compatibility with the target schema without manual intervention.

Related Skills

Explore More Software Engineering Skillsā†’
kangmominkangmomin
1

convention-check-hd

Detect React/Next.js frontend convention violations and generate a structured report.

Community
Advanced
carson-sweetcarson-sweet
6

SweetClaude

Orchestrate project initialization, state migration, and environment health verification for the SweetClaude plugin ecosystem.

Community
Advanced
jabrenajabrena
423

055-design-parallel-change

Design parallel change strategies for database schema and data migrations.

Community
Advanced
adityaarsharmaadityaarsharma
2

orbit-life-upgrade

Detect schema changes and validate idempotent migrations during plugin version upgrades.

Community
Advanced