migrate

Migrate legacy Bifrost v1 inline apps to standalone v2 Solutions.

55|14|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/gobifrost/bifrost --skill migrate-gobifrost
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/gobifrost/bifrost/tree/main/plugins/bifrost/skills/bifrost-migrate
Command: npx skills add https://github.com/gobifrost/bifrost --skill migrate-gobifrost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating legacy Bifrost v1 inline apps to v2 Solutions is a complex, error-prone process that requires rewriting dozens of imports, tracking dependencies, refactoring workflow references, and managing safe cutover to avoid downtime or data loss. This Skill automates and orchestrates the entire end-to-end migration workflow, eliminating manual guesswork and reducing migration risk.

Core Features & Use Cases

  • Deterministic Import Rewriting: Automatically converts v1 bifrost imports to v2-compatible equivalents, installs required shadcn UI components, and scaffolds standalone v2 app structures.
  • Dependency & Reference Management: Tracks full app dependency closures, rewrites workflow references to match organizational naming conventions, and identifies shared entities that cannot be safely captured into a single Solution.
  • Safe Cutover & Verification: Guides users through build verification, zero-downtime slug swapping, and controlled capture of backing entities, with built-in checks to avoid data loss or broken references.
  • Use Case: For example, if you have a legacy Bifrost v1 customer support app hosted in your repo, use this Skill to modernize it to a standalone v2 Solution, standardize its workflow names, and deploy it without disrupting existing user access.

Quick Start

Use the migrate skill to convert your existing Bifrost v1 inline customer support app to a standalone v2 Solution, following the guided workflow to handle import rewrites, dependency setup, and safe deployment cutover.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate legacy Bifrost v1 inline apps to v2 Solutions?

Migrating legacy Bifrost v1 inline apps to v2 Solutions is automated by rewriting imports, scaffolding standalone structures, and managing dependency closures. The process converts existing inline applications into clean, installable standalone Solutions.

What is the best way to refactor workflow references during Bifrost app migration?

Refactoring workflow references during Bifrost app migration involves tracking full app dependency closures and rewriting references to match organizational naming conventions. This standardizes messy workspace configurations and ensures structured Solution capture.

Does the Bifrost v1 to v2 migration support automatic shadcn UI component installation?

Yes, Bifrost v1 to v2 migration supports automatic shadcn UI component installation. It deterministically rewrites v1 bifrost imports to v2-compatible equivalents and installs required shadcn UI components during the standalone app scaffolding process.

Can I achieve zero-downtime slug swapping when modernizing Bifrost v1 apps?

You can achieve zero-downtime slug swapping when modernizing Bifrost v1 apps by following guided build verification and controlled cutover workflows. Built-in checks prevent data loss and broken references during the integration platform transition.

How are shared entities handled when capturing loose workflows into structured Bifrost Solutions?

When capturing loose workflows into structured Bifrost Solutions, shared entities are identified through dependency tracking to prevent unsafe capture. Entities that cannot be safely captured into a single Solution are flagged before the migration completes.