adr-sync

Regenerates the architecture decisions digest in CLAUDE.md from accepted ADR records.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill adr-sync-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-sync
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/adr-sync
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill adr-sync-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project memory in CLAUDE.md drifts out of sync with the ratified Architecture Decision Records, so new sessions start without awareness of the decisions that govern the codebase. This Skill rebuilds a compact, marker-managed digest of accepted ADRs so the project memory always reflects the current ratified corpus. ## Core Features & Use Cases - Accepted-only digest: Reads the ADR corpus via the adr MCP tool and includes only records with accepted status, dropping superseded, deprecated, or rejected entries. - Marker-managed block: Regenerates content strictly between marvin:adr-digest:start and marvin:adr-digest:end markers, leaving all surrounding prose untouched. - Diff-before-write gate: Shows the before/after of the managed block with a summary of added, dropped, and reworded records, and writes nothing without explicit user confirmation. - Use Case: After accepting a new ADR with /marvin:adr-accept, run this Skill to refresh the decisions table in CLAUDE.md so every future session sees the updated ratified corpus. ## Quick Start Ask Claude to sync the architecture decisions digest in CLAUDE.md from the accepted ADR records and show the diff before writing.

Frequently Asked Questions about adr-sync

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

FAQPage Schema
How do I keep CLAUDE.md in sync with my architecture decision records?▼

Run the adr-sync workflow, which lists accepted ADRs via the adr MCP tool and regenerates a one-line-per-decision table inside marker-managed blocks in CLAUDE.md. It shows a diff and asks for confirmation before writing anything.

Which ADR statuses are included in the decisions digest?▼

Only records with accepted status are included. Proposed records carry no authority yet, and superseded, deprecated, or rejected records drop out of the digest on the next regeneration.

What happens if CLAUDE.md has no digest markers yet?▼

The Skill proposes an insertion point near existing architecture prose or at the end of the file, shows the exact insertion, and adds a heading only when inserting fresh. If no CLAUDE.md exists, it offers to create a minimal one, but writes nothing without confirmation.

Will syncing overwrite my hand-written notes in CLAUDE.md?▼

No. Only the content between the marvin:adr-digest:start and marvin:adr-digest:end markers is regenerated. All surrounding prose is left untouched, and the diff is shown for approval before any write occurs.

When should I re-run the ADR digest sync?▼

Re-run it after every ADR lifecycle change, such as accepting a new record or superseding an old one. This keeps the digest honest so each new session starts aware of the current ratified decisions.