schema-unify

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

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill schema-unify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-unify
Source: https://github.com/weiping/gbrain-cn/tree/main/skills/schema-unify
Command: npx skills add https://github.com/weiping/gbrain-cn --skill schema-unify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes type proliferation in an existing GBrain by migrating noisy, legacy page types into gbrain-base-v2’s 14-canonical-type taxonomy (plus a note catch-all) while preserving rollback signals.

Core Features & Use Cases

  • Discovery & Preview: Run onboard checks to confirm the active pack and preview the exact retyping/alias/link changes before applying.
  • Canonical Migration Execution: Uses the unify-types Minion handler to collapse many legacy pages.type values into canonical types via mapping rules.
  • Verification & Rollback Readiness: Ensures post-migration invariants (active pack flip, bounded type count, no dangling aliases) and preserves frontmatter.legacy_type for rollback.

Quick Start

Ask your agent to migrate your brain to gbrain-base-v2 by running a dry-run check first, then submitting the protected unify job to apply the canonical taxonomy.

Frequently Asked Questions about schema-unify

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

FAQPage Schema
How do I clean up type proliferation warnings in my knowledge graph?

To clean up type proliferation warnings in your knowledge graph, you can migrate legacy page types into a 14-type canonical taxonomy using a protected unify-types job. This collapses messy ingestion-specific values into a DRY/MECE schema.

How do I migrate legacy page types to a canonical taxonomy safely?

You can safely migrate legacy page types to a canonical taxonomy by running onboard checks with --check and --explain for a preview, then submitting the unify-types job with --allow-protected to apply the retyping and verify cardinality.

What is a canonical taxonomy migration and when do I need it?

A canonical taxonomy migration consolidates noisy legacy page types into a bounded 14-type schema plus a note catch-all. You need it during onboarding pack upgrades to unify tweets, entities, concepts, and edge-shaped pages into a DRY/MECE structure.

Can I rollback a schema migration if type unification breaks my graph?

Yes, rollback safety is preserved during schema migration by maintaining original values in frontmatter.legacy_type. This ensures you can revert the canonical taxonomy changes if post-migration verification fails or invariants are broken.

Does the unify-types migration work with gbrain-base-v2 onboarding packs?

Yes, the unify-types migration works specifically with gbrain-base-v2 onboarding packs by mapping legacy values from gbrain-base or compatible packs. It executes a target pack flip and runs post-verify checks for alias cardinality.

What are the limitations of collapsing page types into a 14-type schema?

Collapsing page types into a 14-type schema limits your graph to bounded canonical categories plus a single note catch-all. You must run dry-run checks first, as ingestion-specific types are consolidated and cannot retain their original distinct classifications.