project-migrate

Automating documentation migration to a new directory structure uses AI-driven analysis to categorize, move, and update files safely. It handles backup creation and git history preservation while organizing scattered documents into standardized folders.

AI content analysis for file migration uses LLMs to evaluate document content and categorize files into specs, proposals, or ADRs. It automatically generates rich frontmatter metadata and fixes broken relative links within the migrated documents.

Yes, Gemini CLI is a required dependency to execute this documentation migration process. It provides the necessary LLM capabilities for content analysis, categorization, and automated link correction during the file movement workflow.

Yes, you can preserve git history when moving markdown files by using git mv commands during the migration. This ensures version control tracking remains intact while files are reorganized into the new directory structure.

The best way to fix broken relative links after moving documentation files is through LLM-based automated link correction. It analyzes the new file locations and updates internal references to ensure all document paths remain valid post-migration.

When a file conflict is detected during documentation migration, the process creates full backups and provides rollback scripts to ensure zero data loss. This safe migration approach allows you to restore the original state if any issues arise.