docs-migration-pipeline

Solid

Migrate three legacy Markdown docs into Starlight-compatible migration candidates inside an isolated temp repo. Use when you need stage receipts, crash recovery, resume validation, or deterministic candidate packaging without touching real user docs.

AI & Automation 2,589 stars 215 forks Updated 4 days ago NOASSERTION

Install

View on GitHub

Quality Score: 81/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
65
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# docs-migration-pipeline This skill orchestrates a five-stage migration candidate pipeline: 1. `inventory` 2. `normalize` 3. `transform` 4. `validate` 5. `package-candidate` Required reading before execution: - `references/stage-contract.md` Deterministic commands: - Run the pipeline: - `node .agents/skills/docs-migration-pipeline/scripts/run-pipeline.mjs` - Simulate a crash after `transform`: - `node .agents/skills/docs-migration-pipeline/scripts/run-pipeline.mjs --scenario crash-after-transform` - Resume after a checkpoint: - `node .agents/skills/docs-migration-pipeline/scripts/run-pipeline.mjs --resume` - Verify receipt integrity: - `node .agents/skills/docs-migration-pipeline/scripts/verify-receipts.mjs` Execution rules: - Only work inside this isolated fixture repo. - Never overwrite files in `legacy/`. - All stage receipts must include `input_sha`, `output_sha`, `command`, `exit_code`, `status`, and stable sequence fields. - A resume may reuse a stage only when the prior receipt is intact and its `input_sha` still matches the current inputs. - If input hashes drift, stop with stale-resume exit `32`. - If a required receipt is missing or corrupt, stop with receipt-issue exit `33`. - The final artifact is a migration candidate package, not a published doc.

Details

Author
LearnPrompt
Repository
LearnPrompt/LearnPrompt
Created
3 years ago
Last Updated
4 days ago
Language
MDX
License
NOASSERTION

Integrates with

OpenAI · AI Stability AI · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

migration-context

Classifies markdown files in a target project's `docs/` folder and proposes `git mv` commands to relocate agent-flavored content to `.claude/context/`. Use when asked to "migrate docs to context", "move docs to context", "split docs", or to align an existing project with the three-tier context model. Do NOT auto-execute moves or rewrite inbound links. Proposal only.

2 Updated today
erclx
Code & Development Listed

test-migration

Phase 3 of the test-readiness pipeline. Reconciles existing tests against the Phase 1 inventory and Phase 2 blueprint, bucketing each existing test and each inventory item into reuse / promote / rebuild / trim (redundant assertions) / net-new. Same bucketing applies to test infrastructure. Enforces the canonical-layer rule — a test whose assertions are already owned by a lower-layer test gets redundant assertions trimmed, not the test deleted. Writes `docs/test-readiness/test-migration.md`. Invoke when the `/test-migration` command runs.

12 Updated today
app-vitals
API & Backend Listed

migration-safety

Review the migration-safety story for a data-layer change at stage-04d. Use this skill when the user says 'review this migration', 'is this rollback plan solid', '/migration-safety', or when the orchestrator invokes the migrations role for stage-04d. The skill walks schema delta → breaking-change classification → backfill strategy → dual-write strategy → rollback plan → rollback test → gate write. Has veto power on unsafe migrations.

6 Updated today
telus-labs