Project Migrate FAQs

Question 1

When should I use this Claude Code skill?

Accepted Answer

You should use this skill when onboarding 'brownfield' projects to the AgenticDev framework, when reorganizing ad-hoc documentation into a standardized structure, or when you need to enrich existing documents with AI-generated metadata and summaries.

Question 2

Is the migration process safe for my existing data?

Accepted Answer

Yes, safety is a priority. The skill offers a 'dry-run' mode to preview changes and automatically creates a timestamped backup of your documentation along with a 'rollback.sh' script to revert all changes instantly if the results don't meet your expectations.

Question 3

Will using Project Migrate break my Git history?

Accepted Answer

No. The skill is designed to be Git-aware, utilizing native 'git mv' commands during the migration phase. This ensures that all historical data, author contributions, and file versions are fully preserved in your repository.

Question 4

How does AI improve the migration process compared to manual scripts?

Accepted Answer

Unlike standard scripts that rely on filenames, this skill uses the Gemini CLI to read and understand the actual content of your files. This allows for accurate categorization into types like 'specs' or 'proposals' and enables context-aware link updates that pattern-matching often misses.

Question 5

What does the Project Migrate skill do?

Accepted Answer

Project Migrate automates the transition of legacy project documentation into the structured AgenticDev format. It leverages Gemini AI to analyze content for intelligent categorization, corrects relative links, and generates compliant YAML frontmatter while preserving your Git history.

Project Migrate

Project Migrate

主な機能

ユースケース

主な機能

ユースケース