skills.rest
nanograph
nanographOFFICIAL
Explore all skills by this author →
WebsiteGitHub

nanograph-lance

Migrate legacy nanograph storage layouts to NamespaceLineage lineage-native generation.

1|Updated Mar 15, 2026
Search Tags:#migration#backup#storage#cdc#nanograph#lineage-native
One-click install
npx skills add https://github.com/nanograph/nanograph-skills --skill nanograph-lance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nanograph-lance
Source: https://github.com/nanograph/nanograph-skills/tree/main/skills/nanograph-lance
Command: npx skills add https://github.com/nanograph/nanograph-skills --skill nanograph-lance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate a legacy nanograph storage layout to the current NamespaceLineage lineage-native generation, enabling projects to upgrade storage with a clear path, verification, and rollback options.

Core Features & Use Cases

  • One-shot storage migration that preserves the currently committed visible state while resetting storage-era history.
  • Verifiable backups are created to support rollback and safe experimentation.
  • Guidance for when to apply the migration, including legacy manifest or WAL layouts and CDC rail upgrades.

Quick Start

Run the migration with nanograph storage migrate --db <db>.nano --target lineage-native and verify the results before removing the backup.

Frequently Asked Questions about nanograph-lance

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

FAQPage Schema
How do I migrate legacy nanograph storage to a lineage-native generation?▼

Run a one-shot storage migration using nanograph storage migrate --db <db>.nano --target lineage-native to upgrade legacy layouts while preserving the currently committed visible state and resetting storage-era history.

When should I perform a nanograph storage migration?▼

Apply a storage migration when legacy manifest or WAL layouts are detected, when a user requests storage migration, or when upgrading projects to the current CDC rail for new lineage-native generation.

Can I rollback a nanograph storage migration if verification fails?▼

Yes, the migration creates a verifiable backup to support safe rollback. Verify the migration results first, and only remove the backup once the lineage-native storage generation is successfully confirmed.

Does nanograph storage migration preserve committed visible state and historical data?▼

The migration preserves the currently committed visible state exactly as-is, but resets storage-era history. This ensures the lineage-native generation starts cleanly from the current visible state without legacy storage history.

What's the best way to verify a successful lineage-native storage migration?▼

Run the migration command, then verify the results before removing the backup. The one-shot migration provides clear verification steps to confirm the lineage-native generation is functioning correctly before finalizing.

Related Skills

Explore More Software Engineering Skills→
almazomalmazom

observer

Monitor worker pane states and verify wakeup proofs via heartbeat checks.

Community
Advanced
BSchafer01BSchafer01

desktop-shell-maximize-gate

Verify shell chrome visibility across restored and maximized window states.

Community
Intermediate
billynewportbillynewport

Enable SQL Server CDC

Enable CDC on SQL Server databases and tables for change capture.

Community
Advanced
Sumeet138Sumeet138
1

database-migration

Migrate databases across Sequelize, TypeORM, and Prisma without downtime.

Community
Advanced