migrate-posts-to-v2-frontmatter

What problem does it solve?

This Skill solves the risk of breaking a populated content build when a required frontmatter field and validation contract change across many Markdown posts.

Core Features & Use Cases

• Four-phase migration workflow: add a nullable field, backfill, verify, then flip the validator only after sign-off to prevent build outages.
• Per-post safety and rollback: use .bak files and an explicit rollback path that preserves authored content instead of regenerating summaries.
• Controlled tag normalization and schema re-validation: normalize tags to the canonical vocabulary and ensure every post passes the v2 schema before enforcement.
• Verification gates for migration correctness: enforce dry-run review, post-level author confirmation, and zero-error validation before changing the schema requirement.

Quick Start

Run the migration for content/posts/**/*.md in dry-run mode first, review the output, then apply the v2 frontmatter backfill with --apply and flip the validator only after author sign-off.