migrate

Convert legacy ADR Markdown files into the canonical seven-section template.

4|1|Updated Apr 25, 2026

Search Tags:#template #markdown #codebase #decision record #ADR

Ready to run

npx skills add https://github.com/rvdbreemen/adr-kit --skill migrate-rvdbreemen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/rvdbreemen/adr-kit/tree/main/skills/migrate
Command: npx skills add https://github.com/rvdbreemen/adr-kit --skill migrate-rvdbreemen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining consistency and adherence to architecture decision records (ADRs) within a codebase. It converts legacy ADRs into a standardized template, making them easier to enforce and track.

Core Features & Use Cases

Legacy ADR Rewrite: Converts legacy ADRs into a canonical seven-section template, improving compliance with decision enforcement tools.
Status Promotion: Elevates inline status lines to the top-level section.
Structure Enhancement: Reorganizes content to enhance readability and enforceable structure.
Use Case: Automate the migration of existing ADRs to the new template, ensuring that every ADR is structured for compliance with /adr-kit:lint.

Quick Start

Use the migrate skill on the ADR you want to convert. For example, migrate path/to/your/adr.md.

Frequently Asked Questions about migrate

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

FAQPage Schema

How do I convert legacy Architecture Decision Records to a standardized markdown template?▼

You can convert legacy Architecture Decision Records by running the migrate command on your markdown file, such as `migrate path/to/your/adr.md`. It parses and restructures the document into the canonical seven-section template.

What is the canonical ADR format required for codebase compliance?▼

The canonical ADR format is a standardized seven-section markdown template required by the `/adr-kit:lint` tool. It elevates inline status lines to a top-level section to enforce structure and maintainability across decision records.

How do I automate the migration of existing ADRs to enforce a new template structure?▼

Automate ADR migration by applying the migrate skill to your markdown files. It automatically reorganizes content, promotes inline status lines, and rewrites legacy records to match the canonical template for compliance enforcement.

Does the ADR migration process alter the original markdown content or just the structure?▼

The ADR migration process primarily enhances structure by reorganizing markdown content into seven sections and promoting inline status lines to the top level. It standardizes decision records for readability and linting compliance.

When do I need to standardize legacy Architecture Decision Records in my codebase?▼

You need to standardize legacy Architecture Decision Records when your codebase requires compliance with the `/adr-kit:lint` tool, ensuring that all existing markdown decision files adhere to a maintainable, enforceable structure.