pi-migration

Migrate and resync Claude Code projects to the pi platform.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/NewEarthAI/vibecode-project-template --skill pi-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-migration
Source: https://github.com/NewEarthAI/vibecode-project-template/tree/main/.claude/skills/pi-migration
Command: npx skills add https://github.com/NewEarthAI/vibecode-project-template --skill pi-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, pi, pi-mcp-adapter, jq, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill migrates and synchronizes Claude Code projects to the pi platform, ensuring 100% parity in all aspects of the original setup.

Core Features & Use Cases

  • Complete Migration: Moves all skills, agents, prompts, and configuration settings from Claude Code to pi.
  • Resyncing: Keeps an existing pi mirror up to date with any changes made in Claude Code.
  • Use Case: If you are switching from Claude Code to pi or want to maintain a separate mirror for backup, this Skill automates the process and guarantees consistency.

Quick Start

Migrate your project from Claude Code to pi using the pi-migration skill.

Frequently Asked Questions about pi-migration

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

FAQPage Schema
How do I migrate a Claude Code project to the pi platform?

Migrate Claude Code projects to pi by running the pi-migration Skill, which automatically moves all skills, agents, prompts, and configuration settings to guarantee 100% setup parity. It handles MCP consolidation, skill linking, and command conversion.

Can I resync an existing pi mirror after making changes in Claude Code?

Yes, you can resync an existing pi mirror using delta resync to update it with any changes made in Claude Code. This keeps your backup or separate platform mirror fully consistent without repeating the entire initial migration.

Does migrating Claude Code hooks and commands to pi require manual porting?

No manual porting is required because the migration automatically ports hooks to pi extensions and converts commands to prompts. This automated conversion ensures full functional parity during the platform integration process.

What dependencies are needed to run a pi project migration from Claude Code?

To run the pi project migration, you need Node.js, pi, pi-mcp-adapter, jq, and git installed in your environment. These tools facilitate the code conversion, MCP consolidation, and synchronization processes.

Is there a way to verify configuration parity after migrating to the pi platform?

Yes, the migration process includes full verification to ensure 100% parity in all aspects of the original setup, covering model configuration, skills, and agents. This verification confirms the platform integration succeeded.

Why use a dedicated migration tool instead of manually copying files to pi?

A dedicated migration tool automates complex transformations like hook-to-extension porting, command-to-prompt conversion, and MCP consolidation that manual copying cannot handle. This guarantees full setup parity and enables delta resyncing.