migrate-docs

Migrate documentation structures to ai-dev standards with backups and validation.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aifuun/u-safe-archive --skill migrate-docs-aifuun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-docs
Source: https://github.com/aifuun/u-safe-archive/tree/main/.claude/skills/migrate-docs
Command: npx skills add https://github.com/aifuun/u-safe-archive --skill migrate-docs-aifuun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual documentation migrations are error-prone and time-consuming, especially when adopting ai-dev standards across multiple projects. This skill automates the entire workflow to safely move existing docs into a standardized ai-dev structure.

Core Features & Use Cases

  • Backup existing documentation by renaming docs/ to docs.old/ to preserve a restore point.
  • Rebuild the standard ai-dev docs structure via an initialization step (/init-docs) and copy the manual references.
  • Generate a comprehensive migration map and execute content migration with visibility for required manual review.
  • Validate the new structure with a baseline and final checks to ensure compliance, plus a generated migration report.
  • Use cases include migrating buffers, u-safe, or any project to ai-dev doc standards with rollback safety.

Quick Start

Run /migrate-docs <target-project-path> to begin migrating documentation to ai-dev standards.

Frequently Asked Questions about migrate-docs

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

FAQPage Schema
How do I migrate legacy documentation to ai-dev standards safely?

Documentation migration to ai-dev standards is automated by backing up existing docs to a restore point, rebuilding the standardized structure, and executing content migration with final validation checks.

What is the best way to automate moving existing docs into a standardized structure?

Automating docs migration involves generating a comprehensive mapping of legacy content, executing the transfer into the new layout, and producing a validation report to ensure structural compliance.

How does the backup process work during a documentation structure migration?

The backup process preserves original files by renaming the existing docs directory to docs.old, providing a rollback restore point before the new ai-dev structure is initialized and populated.

Do I need to manually review content when migrating documentation layouts?

Yes, while the migration map and content transfer are automated, the process provides visibility for required manual review to ensure specific legacy content aligns correctly within the new ai-dev structure.

Can I validate the new documentation structure after migration is complete?

Yes, documentation validation is performed using baseline and final checks to ensure the newly migrated structure complies with ai-dev standards, culminating in a generated migration report.

What are the limitations of automated docs migration for multiple projects?

Automated docs migration requires a manual review phase for complex content mapping and relies on initializing a standard structure, meaning highly customized legacy layouts may need manual adjustments before final validation.