agentleFS
rust-worksrust-works/omni-dev/.claude/skills/update-adr-inventory/SKILL.md

update-adr-inventory

Skill2 starsChanged 39 days agoBSD-3-ClauseView on GitHub

Update the ADR inventory table in docs/adrs/README.md by scanning all adr-*.md files, extracting their title, status, and date. Use when a new ADR is added or an existing ADR's status or title has changed.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Date: Use the git log to find the commit date when the file was first added:

    line 17
  2. Distinctive:

    If the file is untracked (not yet committed), use today's date.

    line 21
  3. Very specific:

    Read all adr-*.md files in docs/adrs/

    line 48
  4. Distinctive:

    Look up the git creation date for each file

    line 50
  5. Distinctive:

    Ensure the table is formatted with consistent column widths

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update ADR Inventory Skill

This skill updates the inventory table in docs/adrs/README.md to reflect the current set of ADR files.

Process

  1. Scan docs/adrs/ for all files matching adr-*.md
  2. Extract from each file:
    • ADR number from the filename (e.g., adr-0003.md -> ADR-0003)
    • Title from the # ADR-NNNN: <Title> heading on line 1
    • Status from the ## Status section (line after the heading, e.g., ✅ Accepted). If the line ends with a trailing parenthesized date (e.g., 🔄 Superseded by [ADR-0022](adr-0022.md) (2026-05-06)), strip that trailing (YYYY-MM-DD) — the supersession date already appears in the Date column. Preserve the rest verbatim, including any successor link.
  3. Date: Use the git log to find the commit date when the file was first added:
    git log --diff-filter=A --format=%as -- docs/adrs/adr-NNNN.md
    If the file is untracked (not yet committed), use today's date.
  4. Rebuild the inventory table in docs/adrs/README.md, sorted by ADR number ascending
  5. Format the table using the format-table skill for consistent column widths

Table Format

The inventory table uses this structure:

## Inventory

| ADR                      | Status      | Date       | Title                             |
|--------------------------|-------------|------------|-----------------------------------|
| [ADR-0000](adr-0000.md)  | ✅ Accepted | 2026-02-10 | Use Architecture Decision Records  |

Column Details

ColumnSourceExample
ADRFilename, linked: [ADR-NNNN](...)[ADR-0000](adr-0000.md)
StatusStatus section, trailing (date) stripped✅ Accepted / 🔄 Superseded by [ADR-NNNN](adr-NNNN.md)
DateGit first-commit date or today2026-02-10
TitleH1 heading after ADR-NNNN: Use Architecture Decision Records

Instructions

  1. Read all adr-*.md files in docs/adrs/
  2. For each file, extract the title from line 1 and status from the Status section
  3. Look up the git creation date for each file
  4. Replace the inventory table section in docs/adrs/README.md with the updated table
  5. Ensure the table is formatted with consistent column widths

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.