migrate

Migrate personal content from a 2bd engine repository to a separate vault directory.

4|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/BugRoger/2bd --skill migrate-bugroger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/BugRoger/2bd/tree/main/.claude/skills/actions/migrate
Command: npx skills add https://github.com/BugRoger/2bd --skill migrate-bugroger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users transition from a single repository containing both the 2bd engine code and their personal notes to a cleaner setup where the engine is in a dedicated Git repository and personal content resides in a separate "vault" directory.

Core Features & Use Cases

  • Content Separation: Moves personal notes (Captive, Periodic, Projects, etc.) from the engine repository to a designated vault.
  • Configuration Update: Creates or updates the .claude/config.md file to point to the new vault location.
  • Cleanup Guidance: Provides clear instructions on how to remove the migrated content from the engine repository to maintain a clean separation.
  • Use Case: You've been using 2bd with all your notes in the same Git repo. Now you want to share the engine code publicly or keep your personal notes separate for better organization and cloud syncing.

Quick Start

Run the migrate skill, providing the path to your desired vault directory.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I separate personal notes from a 2bd engine repository?

Separating personal notes from a 2bd engine repository involves migrating your content to a designated vault directory. This tool validates the vault path, copies specified content types, and updates the engine configuration to reflect the new location.

What is the best way to split engine code and user data in a Git workflow?

Splitting engine code and user data in a Git workflow is achieved by moving personal content into a separate vault directory. This separation facilitates cleaner repository management, allowing the engine code to remain isolated in a dedicated Git repository.

Does migrating content to a separate vault update the engine configuration automatically?

Migrating content to a separate vault updates the engine configuration automatically. The migration process creates or updates the `.claude/config.md` file to point directly to your newly designated vault location.

How do I clean up the original repository after moving content to a vault?

Cleaning up the original repository after moving content to a vault requires following the provided cleanup guidance. The migration tool outputs clear instructions on how to remove the migrated personal notes from the engine repository to maintain a clean separation.

When do I need to separate my 2bd engine code from my personal content?

Separating 2bd engine code from personal content is necessary when you want to share the engine code publicly or keep your personal notes separate for better organization and cloud syncing. This separation improves overall maintainability.