create-adr

Create Architecture Decision Records from pull request metadata and diffs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zorgentech/archon --skill create-adr-zorgentech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/zorgentech/archon/tree/main/.claude/skills/create-adr
Command: npx skills add https://github.com/zorgentech/archon --skill create-adr-zorgentech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of Architecture Decision Records (ADRs) so that architectural choices introduced by pull requests or manual proposals are consistently documented, tracked, and reviewed without manual file creation and formatting.

Core Features & Use Cases

  • Automatic ADR generation from PRs: Extracts PR title, body, and file diffs to populate context, options, and justification sections.
  • Template-driven output and bookkeeping: Uses the project ADR template, saves new ADRs as proposed in docs/adr/potential-adr/, and updates the ADR README with a pending entry.
  • Interactive or manual modes: Accepts a PR number, a free-form decision description, or prompts the user to supply input for cases where automation cannot infer all details.
  • Use case: During code review, run this Skill on a PR that includes architectural changes to produce a draft ADR ready for review and approval.

Quick Start

Run the create-adr skill with a Pull Request number or a textual description to produce a proposed ADR in docs/adr/potential-adr/ and update the ADR README.

Frequently Asked Questions about create-adr

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

FAQPage Schema
How do I automatically generate architecture decision records from pull requests?

To automatically generate architecture decision records from pull requests, the Skill extracts PR metadata and file diffs to populate context, options, and justification sections. It writes the completed ADR file to the repository using a standard template.

What is the best way to document architectural choices introduced by a pull request during code review?

Documenting architectural choices during code review is handled by generating a draft ADR from the PR diff and metadata. The Skill creates a proposed record in docs/adr/potential-adr/ and updates the ADR README with a pending entry for review.

Can I create an ADR from a manual description instead of a GitHub pull request?

Yes, you can create an ADR from a manual description. The Skill accepts a free-form decision description or prompts you to supply input, allowing you to document architectural choices when automation cannot infer all details.

Does generating ADRs from pull requests require write permissions to the repository?

Generating ADRs from pull requests requires repository access and write permissions. The Skill needs these permissions to inspect PR diffs, write the new ADR file to docs/adr/potential-adr/, and update the ADR README.

How does the ADR automation handle the MADR template and project bookkeeping?

ADR automation handles the MADR template by populating it with extracted PR data and saving it as a proposed file. For bookkeeping, it updates docs/adr/README.md with a pending entry to maintain a tracked list of proposed architectural decisions.