project-migrate

Migrate existing project documentation into the AgenticDev structure with backups and link correction.

11|3|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/bodangren/git-workflow --skill project-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-migrate
Source: https://github.com/bodangren/git-workflow/tree/main/.claude/skills/project-migrate
Command: npx skills add https://github.com/bodangren/git-workflow --skill project-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gemini-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of migrating existing project documentation into the structured AgenticDev format, ensuring consistency and preserving history.

Core Features & Use Cases

  • AI-Powered Discovery: Intelligently analyzes existing markdown files to determine their correct type (spec, proposal, ADR, etc.).
  • Safe Migration: Creates a full backup with a rollback script before making any changes, preserving git history with git mv.
  • LLM-Enhanced Link Correction: Uses AI to fix broken relative links within migrated files.
  • Use Case: You're adopting AgenticDev for a legacy project with years of scattered documentation. This skill will scan your docs/, documentation/, and root directories, categorize each file, move them to the appropriate docs/specs/, docs/changes/, or docs/ subdirectories, and update internal links, all while providing a safety net for rollback.

Quick Start

Run the project-migrate script interactively to begin migrating your existing documentation.

Frequently Asked Questions about project-migrate

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

FAQPage Schema
How do I migrate existing project documentation to a new structure?

To migrate existing project documentation to a new structure, this Skill uses AI-driven content analysis to discover, categorize, and move scattered markdown files into appropriate subdirectories while preserving git history. It requires Python scripts and Gemini CLI for advanced analysis.

Can I automatically categorize markdown files when adopting a new project structure?

Yes, you can automatically categorize markdown files when adopting a new project structure. The Skill intelligently analyzes existing markdown files to determine their correct type, such as specs, proposals, or ADRs, using AI-powered discovery.

What is the best way to fix broken relative links in migrated markdown files?

The best way to fix broken relative links in migrated markdown files is using LLM-enhanced link correction. The Skill leverages AI to automatically identify and update internal links within migrated files during the structural transition.

Do I need Gemini CLI to automate documentation migration?

Yes, you need Gemini CLI to automate documentation migration with this Skill. It requires the Gemini CLI dependency to perform advanced AI-driven content analysis and categorization for your brownfield projects.

How do I safely backup files before refactoring project documentation?

To safely backup files before refactoring project documentation, the Skill creates a full backup with a rollback script before making any changes. It also preserves git history by using git mv for file operations.

What are the limitations of using AI for brownfield project migration?

Limitations of using AI for brownfield project migration include the requirement of specific dependencies like Gemini CLI and Python scripts. The process targets scattered markdown files and relies on automated categorization, meaning non-markdown formats are out of scope.