迁移代码文档 · Doc Migrator

    1

    把旧格式代码文档安全迁移到新仓库/新平台:盘点引用、改写路径与版本标注,带回滚方案与遗漏检查。 Migrate legacy docs safely to a new repo or platform: inventory references, rewrite paths, tag versions, and get a rollback plan plus a gap-check list.

    $7

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    迁移代码文档 · Doc Migrator

    Example session with this skill installed

    我们想把 Confluence 上的 30 篇接口文档迁到 Git 仓库，里面有不少截图和指向旧域名的链接。请给我一份能落地的迁移方案，包括盘点清单和回滚办法。
    We want to move 30 API docs from Confluence to a Git repository. Many contain screenshots and links to the old domain. Please give me a practical migration plan with an inventory list and rollback steps.

    • Read your context and instructions
    • Compiled the doc migrator

    结论：这次迁移的难点不是「搬运」，而是「断链」。30 篇文档里有截图与旧域名链接，直接搬会导致大量 404。正确做法是：先盘点引用清单，再按「直接搬→改写链接→人工确认」三类分批处理，全程保留回滚点。
    Conclusion: the hard part is not moving files but avoiding broken links. With screenshots and old-domain URLs across 30 docs, a direct move would cause many 404s. Inventory references first, then batch the work into move-as-is, rewrite-links, and human-review groups, keeping rollback points throughout.

    迁移方案 · Migration plan

    文档类型数量（估算）处理方式验收标准
    纯文本接口说明18 篇直接搬入 docs/api/标题、参数表、示例代码完整
    含截图文档8 篇图片统一移入 images/ 并改写相对路径预览中每张图都能正常显示
    含旧域名链接4 篇替换为 docs.example.com 新路径抽查 20 个链接全部 200
    待人工确认（含过时内容）0-2 篇打「待确认」标记后搬运标记可见，负责人已分配

    分步执行 · Step-by-step

    1. 盘点：导出所有页面与附件清单，记录每篇文档的图片数、外链数。
    2. 分批搬运：先搬纯文本，再搬含图文档，最后处理旧链接文档，每批完成即抽查。
    3. 改链接：用统一脚本把「旧域名/docs.xxx」批量替换成新路径，替换前先备份原文件。
    4. 抽查：迁移完成后随机抽查 10 篇文档的图片与链接，全绿才算完成。

    回滚办法 · Rollback

    • 每搬一批就打一个 Git 标签（如 migrate-batch-1），出错时直接 git revert 该标签。
    • 原 Confluence 空间保留 30 天只读，作为对照源，30 天后归档。

    下一步 · Next steps

    1. 把 30 篇文档的导出文件发我，我按上面的分类表逐篇打标签。/ Send me the exported files and I will tag each doc against the classification table.
    2. 告诉我新仓库的目录结构偏好，我把「docs/api/」替换成你们现有的路径。/ Tell me your preferred directory layout so I can swap docs/api/ for your paths.
    3. 如果截图很多（超过 200 张），建议先压缩图片再上传，我可以补充压缩步骤。/ If there are more than 200 screenshots, compress images before upload; I can add those steps.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Generate structured migration reports with clear, bottom-line conclusions.Identify hidden risks when moving legacy code to modern frameworks.Create simplified onboarding guides for junior developers or new hires.Standardize technical terminology across dual-language documentation.

    About this skill

    它解决什么问题 · The problem

    代码文档散落在旧 wiki、旧仓库和本地笔记里，换平台时最容易丢链接、丢图。这个技能把迁移做成可回滚的流程，先盘点再搬运，避免文档断链和版本错乱。

    Docs scattered across old wikis, repos, and local notes lose links and images when platforms change. This skill turns migration into a rollback-safe process: inventory first, then move, so nothing breaks or gets lost.

    这个技能做什么 · What it does

    它先收集旧文档的位置、格式与引用关系，再输出分步迁移方案：哪些直接搬、哪些要改写链接、哪些需要人工确认，并附迁移后抽查清单与回滚步骤。

    It collects locations, formats, and reference links first, then outputs a step-by-step plan: what to move as-is, what needs link rewrites, and what needs human review — plus a post-migration spot-check list and rollback steps.

    为什么比裸提示词强 · Why it beats raw prompts

    • 先盘点引用关系再动手，减少断链 / Inventory references before moving to cut broken links
    • 每一步都有验收标准，搬没搬对一目了然 / Every step has an acceptance check, so mistakes are visible
    • 自动标出图片、代码块等高风险内容 / Auto-flags high-risk content like images and code blocks
    • 带回滚方案，失败时能退回原状 / Includes a rollback plan to restore the original state

    典型用例 · Typical use cases

    • 团队 wiki 迁移到 Git 仓库文档 / Migrating team wikis into Git-based docs
    • README 等文档从老仓库迁到新仓库 / Moving READMEs and docs between repositories
    • 本地笔记批量转成项目文档 / Converting local notes into project documentation
    • 文档站换域名后的路径批量改写 / Rewriting paths in bulk after a domain change

    局限 · Limitations

    输出迁移方案与检查清单，不执行实际的服务器或仓库操作；批量移动文件仍需你在工具中完成。

    It delivers plans and checklists but does not run server or repository operations; bulk file moves still need to be done in your tools.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    Frequently Asked Questions