skills.rest
inbrainfun
inbrainfunCOMMUNITY
Explore all skills by this author →
𝕏@inbrain_funGitHub

schema-unify

Migrate brain schemas from inbrain-base to inbrain-base-v2 by collapsing page types.

174|144|Updated Jun 10, 2026
Search Tags:#migration#canonical#taxonomy#onboard#unify-types#inbrain
One-click install
npx skills add https://github.com/inbrainfun/inbrain --skill schema-unify-inbrainfun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schema-unify
Source: https://github.com/inbrainfun/inbrain/tree/main/skills/schema-unify
Command: npx skills add https://github.com/inbrainfun/inbrain --skill schema-unify-inbrainfun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating a brain from inbrain-base to inbrain-base-v2 consolidates 94 noisy page types into 15 canonical types (with subtypes, alias rows, and edge-case handling) to enable a safer, upgrade-ready taxonomy while preserving rollback traces.

Core Features & Use Cases

  • Phase-driven migration workflow covering discovery, preview, apply, verify, and post-migration checks with guardrails.
  • Safe, rule-based transformation that creates slug_aliases for redirects, real link rows for edge-shaped pages, and a legacy_type marker for rollback.
  • Clear migration path for large brains, enabling predictable upgrades across packs with minimal data loss and auditable outcomes.

Quick Start

Run the onboarding and unify-types workflow with explicit protection as described in the plan.

Frequently Asked Questions about schema-unify

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

FAQPage Schema
How do I consolidate page types during a brain schema migration?▼

Brain schema migration consolidates 94 noisy page types into 15 canonical types with subtypes, alias rows, and edge-case handling to enable a safer, upgrade-ready taxonomy while preserving rollback traces.

How do I run a safe page type cleanup for large brains?▼

Run inbrain onboard --check, review the dry-run explain output, and submit the protected unify-types job targeting inbrain-base-v2 to execute a phase-driven migration workflow with discovery, preview, apply, verify, and post-migration guardrails.

What does a canonical taxonomy migration do to legacy page types?▼

A canonical taxonomy migration applies rule-based transformations that create slug_aliases for redirects, real link rows for edge-shaped pages, and a legacy_type marker for full rollback traceability.

When should I migrate my brain from inbrain-base to inbrain-base-v2?▼

You should migrate when your brain is flagged with pack_upgrade_available or type_proliferation, or when you explicitly request canonical taxonomy guidance and need to clean up numerous distinct page types.

Can I roll back a unify-types schema migration after applying it?▼

Yes, rollback is possible because the transformation creates a legacy_type marker for each migrated page and generates slug_aliases for redirects, ensuring predictable upgrades with minimal data loss and auditable outcomes.

Related Skills

Explore More Software Engineering Skills→
weipingweiping
1

schema-unify

Migrate legacy GBrain page types to the gbrain-base-v2 14-type taxonomy.

Community
Advanced
italosilva18italosilva18

migration-planner

Plan and execute database, server, and cloud provider migrations with backup and rollback.

Community
Advanced
stratagastrataga

nextjs-request-url-proxy-redirect

Replace request.url with a public base URL from NEXT_PUBLIC_APP_URL for Next.js redirects.

Community
Intermediate
outfitter-devoutfitter-dev
6

patterns

Document Outfitter Stack handler contracts, Result<T, E> types, and error taxonomy.

Official
Intermediate