docs-migrate

Migrate scattered documentation into a unified target structure without duplication.

615|491|Updated Jan 4, 2022
One-click install
npx skills add https://github.com/LedgerHQ/ledger-live --skill docs-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-migrate
Source: https://github.com/LedgerHQ/ledger-live/tree/main/.agents/skills/docs-migrate
Command: npx skills add https://github.com/LedgerHQ/ledger-live --skill docs-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often ends up scattered across multiple files and pages with overlapping or outdated content. This Skill provides a structured process to consolidate, deduplicate, and reorganize docs into a clean target structure.

Core Features & Use Cases

  • Source-to-Target Mapping: Identify source documents and decide where each piece of content belongs in the new structure.
  • Deduplication and Refinement: Detect overlapping content between source and target, then decide what to keep, refine, or discard.
  • Planned or Direct Migration: Produce a migration plan for review, or execute the migration directly when instructed.
  • Use Case: When a repository accumulates READMEs, wiki pages, and ad-hoc notes covering the same topics, use this Skill to consolidate them into a coherent docs hierarchy without losing important content.

Quick Start

Migrate the content from the old onboarding notes into our target docs structure and remove the duplicated sections.

Frequently Asked Questions about docs-migrate

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

FAQPage Schema
How do I migrate scattered documentation into one structure?

Identify the source files, choose their target locations in the new structure, detect duplication between them, then decide what to keep, refine, or discard. The Skill produces a plan first, or performs the migration directly if instructed.

How to consolidate duplicate docs without losing content?

Compare the source and target content to find overlaps, then keep the most complete version and refine it rather than copying both. Content is prioritized over format, and the target structure defines the final organization.

Can I review a migration plan before docs are changed?

Yes. By default the Skill outputs a migration plan describing what will be updated, created, and deleted. The actual migration from step five only happens when you explicitly instruct it to proceed.

Does docs migration work for agent-facing documentation?

Yes. The Skill handles both human-facing and agent-facing documentation. Its description explicitly covers migrating and cleaning up agentic docs alongside regular documentation sources.

When should I not use a docs migration workflow?

Avoid it when writing brand-new documentation with no existing sources, since there is nothing to consolidate. In that case, use a docs creation workflow such as the referenced docs-update-or-create Skill directly.