bear-migrate

Guide database, component, and content migrations through a five-phase process.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill bear-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bear-migrate
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/bear-migrate
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill bear-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, safe, and thorough process for migrating any type of data, component, or system, ensuring completeness and minimizing risk.

Core Features & Use Cases

  • Phased Migration: Follows a deliberate WAKE -> GATHER -> MOVE -> HIBERNATE -> VERIFY flow.
  • Domain-Specific Guidance: Offers tailored references for database, component, content, and general migrations.
  • Safety First: Emphasizes preserving originals, verifying thoroughly, and communicating progress.
  • Use Case: Migrating a legacy database schema to a new structure, upgrading a core UI component library, or consolidating asset file formats across a project.

Quick Start

Use the bear-migrate skill to migrate the database schema for user profiles.

Frequently Asked Questions about bear-migrate

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

FAQPage Schema
What is the safest way to approach a complex database schema migration?

A safe database schema migration requires a structured phased approach that preserves originals, inventories existing schemas, executes changes deliberately, and verifies completeness. This minimizes risk and ensures no data loss during the system upgrade.

How do I migrate a legacy UI component library to a new framework?

Migrating a UI component library involves a five-phase process: prepare the target environment, gather a complete inventory of existing components, execute the component move, verify behavior during a resting phase, and confirm final system integrity.

Can I use a structured migration process for consolidating asset file formats?

Yes, structured migration processes support consolidating asset file formats by providing domain-specific references and anti-pattern guidance. This ensures content assets are safely and thoroughly converted across your project without losing fidelity.

Does this migration process support both data and system upgrades simultaneously?

Yes, this migration process supports simultaneous data and system upgrades by providing tailored references for database, component, content, and general migrations. It guides safe execution while preserving original systems during the transition.

What are the common anti-patterns to avoid during a data migration?

Common data migration anti-patterns involve skipping the inventory phase, failing to preserve original data, and neglecting thorough verification before confirming completion. Avoiding these ensures a patient, safe, and thorough migration across all targeted domains.

Why does a thorough migration process include a separate verification and confirmation phase?

A thorough migration process includes separate verification and confirmation phases to ensure moved data behaves correctly in its new environment before finalizing. This deliberate resting period catches integration issues and confirms complete system integrity.