project-migrate

The project-migrate skill is designed for developers and AI agents looking to adopt the AgenticDev methodology within existing 'brownfield' codebases. Instead of performing a blind file relocation, this tool employs the Gemini CLI to perform deep content analysis on markdown documents. It intelligently interprets the intent and context of each file—identifying specifications, research logs, and technical proposals—to map them into the standardized AgenticDev directory structure. By ensuring that documentation is not just moved, but logically categorized and enriched with metadata, it creates a searchable and compliant project environment ready for agentic workflows.

• Automated discovery and intelligent categorization of legacy documentation including docs/, wiki/, and markdown files.

• Deep content analysis using Gemini to determine document types such as specs, ADRs, and PRDs.

• Preservation of Git file history using atomic git mv commands, ensuring seamless tracking of document evolution.

• Robust LLM-based link updates that understand document context, effectively repairing relative links that break during structural changes.

• Automatic generation of compliant YAML frontmatter, ensuring every document contains a title, type, and descriptive summary.

• Safety-first architecture providing a full timestamped backup and a generated rollback.sh script before any file system operations occur.

• The skill provides three operational modes: interactive for manual oversight, dry-run for previewing migration plans, and auto-approve for CI/CD integration.

• Requires the Gemini CLI to be installed, authenticated, and accessible in the system path for LLM-assisted analysis.

• It is highly recommended to run the doc-indexer skill after the migration process to verify full compliance and directory index integrity.

• Designed for technical teams who need a reliable, non-destructive way to unify documentation standards across sprawling repositories.

• Always review the migration plan in the console before proceeding, and ensure your git workspace is clean prior to execution to facilitate easy rollbacks if necessary.