adr-backfill

Reconstructs MADR-formatted ADRs from git history, specs, and docs.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Nathanto-ai/liza-private --skill adr-backfill-nathanto-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-backfill
Source: https://github.com/Nathanto-ai/liza-private/tree/main/skills/adr-backfill
Command: npx skills add https://github.com/Nathanto-ai/liza-private --skill adr-backfill-nathanto-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backfill ADRs from commits and documentation to preserve architectural decisions after the fact.

Core Features & Use Cases

  • Clustering of commits and specs to surface decisions
  • Enrichment with cross-references and related docs
  • Reproducible MADR-formatted ADR outputs with state management

Quick Start

Reconstruct ADRs from the latest repository history and specs to generate missing decisions.

Frequently Asked Questions about adr-backfill

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

FAQPage Schema
How do I reconstruct architecture decision records from existing git history and documentation?

Reconstructing architecture decision records from git history involves analyzing commits and specs to cluster distributed architectural changes. The process enriches decisions with cross-references and outputs reproducible MADR-formatted ADR markdown files.

What is ADR backfilling and when do I need to generate missing architecture decisions?

ADR backfilling preserves architectural decisions after the fact by analyzing existing repository history and documentation. You need it when decisions were made without recording ADRs, requiring classification and chronological ordering to generate missing records.

How to generate MADR-formatted ADR files from scattered commits and specs?

To generate MADR-formatted ADR files, the system clusters commits and specs to surface decisions, enriches them with related docs, and applies state management to persist outputs as markdown files under specs/architecture/ADR with source links.

Can I backfill ADRs for codebases with distributed architectural changes across multiple commits?

Yes, backfilling ADRs specifically applies to codebases with distributed architectural changes. It handles this by classifying and clustering related commits, enriching them with cross-references, and chronologically ordering them into MADR outputs.

Does generating ADRs from repository history require manual linking to source material?

Generating ADRs from repository history does not require manual linking. The process automatically enriches ADR outputs with cross-references to related docs and links back to the original source material found in git history and specs.

What are the limitations of backfilling architecture decisions from git history?

Backfilling architecture decisions relies entirely on the context available in existing git history and documentation. If architectural changes were made without descriptive commits or supporting specs, the reconstructed ADRs may lack complete decision context.