mj-agent-doc-migrate

Migrates versioned canonical docs to archive directories with frontmatter and wikilink updates.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-doc-migrate-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mj-agent-doc-migrate
Source: https://github.com/MJ-AgentLab/mj-agent/tree/main/.claude/skills/mj-agent-doc-migrate
Command: npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-doc-migrate-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Versioning canonical documentation in the mj-agent repository requires coordinated file moves, frontmatter state changes, archive banners, and corpus-wide wikilink audits. Doing this manually risks broken links, inconsistent states, and lost history. This Skill orchestrates the full Major.Minor archive workflow per ADR-011 and ADR-014. ## Core Features & Use Cases - Standard version archive: Moves the old version to docs/archive/<subdir>/ via git mv, flips state to deprecated, adds an archive banner, and promotes the new version to active. - Skeleton-first delayed promote: Handles the ADR-014 variant where a new draft coexists with the old active version across multiple PRs before a single promote PR. - Living vs frozen reference audit: Greps the corpus for wikilinks to the old version, classifies each as living (upgrade to new version) or frozen (pin to archive path), and syncs INDEX.md. - Use Case: When promoting mj-agent docs from v2.0 to v2.1, run this Skill to archive the old trio, activate the new trio, update all references, and validate with check_frontmatter.py and check_wikilinks.py. ## Quick Start Ask the agent to archive the old version and promote the new one, for example: run the doc migrate workflow to move STANDARD Meta Framework v2.0 to archive and promote v2.1 to active.

Frequently Asked Questions about mj-agent-doc-migrate

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

FAQPage Schema
How do I archive an old version of a versioned markdown document?▼

Use git mv to move the old file into docs/archive/<subdir>/ while keeping its _vX.Y suffix, then set its frontmatter state to deprecated and add an archive banner pointing to the new version. Finally audit all wikilinks referencing the old file.

What is the difference between standard archive and skeleton-first promote?▼

Standard archive handles a single version bump where the old file moves to archive and the new one lands in the same PR. Skeleton-first delayed promote lets a new draft coexist with the old active version across multiple PRs before one promote PR flips all states at once.

When should I not trigger the doc archive workflow?▼

Skip it for daily typo fixes, formatting tweaks, minor revisions, or frontmatter metadata adjustments, since those stay in place per the in-place edit principle. It is also not for writing brand new documents or physically deleting legacy files.

How are living and frozen wikilink references handled during migration?▼

Living references that describe the current state of the project are upgraded to point at the new version. Frozen references that describe historical rules or incidents stay pinned to the old version with an added archive path prefix.

Does the archive workflow delete old documentation files?▼

No, physical deletion is explicitly rejected by ADR-011. The workflow only moves files into the archive directory, preserving history and enabling cite-by-vintage references to older versions.