migrate

Migrates legacy SQLite or chitta data into the current soul context.

3|3|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/genomewalker/cc-soul --skill migrate-genomewalker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/genomewalker/cc-soul/tree/main/skills/migrate
Command: npx skills add https://github.com/genomewalker/cc-soul --skill migrate-genomewalker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of migrating existing soul data from older formats like SQLite databases or shared chitta files into the current CC-Soul system, ensuring data continuity and accessibility.

Core Features & Use Cases

  • Data Source Flexibility: Supports importing data from both SQLite soul.db files and shared chitta files.
  • Guided Import Process: Includes a dry-run option to preview changes before committing to the import.
  • Verification: Confirms the successful import by checking the soul_context and recalling "wisdom".

Quick Start

Use the migrate skill to import data from your SQLite soul.db file.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate soul data from a legacy SQLite database?

To migrate soul data from a legacy SQLite database, this skill facilitates incremental import by identifying the data source and verifying the imported records within the soul context.

Can I preview data changes before importing chitta files?

You can preview data changes before importing chitta files by using the guided dry-run option to review modifications and ensure accuracy before committing to the migration.

Does the CC-Soul migration process support shared chitta files?

The CC-Soul migration process supports shared chitta files, allowing you to import existing soul data alongside legacy SQLite databases to ensure data continuity.

How do I verify data after importing to the soul context?

You verify data after importing to the soul context by checking the soul_context and recalling wisdom to confirm the successful incremental import of your legacy records.

What is the best way to incrementally import legacy soul data?

The best way to incrementally import legacy soul data is using a guided process that identifies sources, performs a dry-run for approval, and verifies the imported data.