migrate-to-guidance

Migrate CLAUDE.md files into .rpiv/guidance as architecture.md and update references.

581|102|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill migrate-to-guidance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-guidance
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/migrate-to-guidance
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill migrate-to-guidance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate CLAUDE.md files into the .rpiv/guidance system by relocating content and normalizing references.

Core Features & Use Cases

  • Locate all CLAUDE.md files across a project and relocate them into the guidance shadow tree as architecture.md equivalents.
  • Update cross-references to point to the new .rpiv/guidance paths, preserving linkage and intent.
  • Use cases include converting legacy annotations into centralized guidance for consistent downstream tooling.

Quick Start

Run the migration against your codebase to move CLAUDE.md into guidance and wire up references.

Frequently Asked Questions about migrate-to-guidance

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

FAQPage Schema
Can I preview a CLAUDE.md migration before applying changes?

Yes, you can preview a CLAUDE.md migration before applying changes by running the script in dry-run mode, which shows the planned file relocations and cross-reference updates without modifying your project.

Does the migration script support deleting original CLAUDE.md files after moving them?

The best way to update cross-references when relocating CLAUDE.md is using an automated migration script that rewrites paths to point to the new .rpiv/guidance locations, preserving existing linkage and intent.

What pre-flight checks are needed before converting CLAUDE.md files to architecture.md?

Yes, the migration script supports deleting original CLAUDE.md files after moving them when explicitly requested, ensuring no duplicate content remains in the project directory structure.

Why does my project need centralized guidance files instead of CLAUDE.md?

Pre-flight checks before converting CLAUDE.md files to architecture.md verify project readiness by scanning for existing files in the .rpiv/guidance shadow tree and validating cross-reference paths to prevent migration conflicts.