rust-worksrust-works/omni-dev/.agents/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

rust-works/succinctlyedited, first seen Oct 9, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
rust-works/succinctly★ 5210% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- changelogSkill
- commit-twiddleSkill
- format-tableSkill
- releaseSkill
- update-snapshotsSkill
- version-bumpSkill
- changelogSkill
- commit-twiddleSkill
- format-tableSkill
- releaseSkill
- update-adr-inventorySkill
- update-snapshotsSkill
- version-bumpSkill

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

Distinctive:
Date: Use the exact path found in step 1 to find the commit date when the file was first added, including any filename suffix:
line 26
Distinctive:
If the file is untracked (not yet committed), use today's date.
line 30
Very specific:
Read all adr-*.md files in docs/adrs/
line 57
Distinctive:
Look up the git creation date for each file
line 59
Distinctive:
Ensure the table is formatted with consistent column widths
line 61

≈ “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

Scan docs/adrs/ for all files matching adr-*.md
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 first nonblank paragraph under ## Status:
  - Extract only the status label: 🟡 Proposed, ✅ Accepted, ❌ Deprecated, or 🔄 Superseded.
  - For a superseded ADR, retain by [ADR-NNNN](actual-filename.md) when present.
  - Omit dates, amendment notes, and other explanatory prose even when they follow a date or wrap onto another line. For example, ✅ Accepted (2026-05-06) — supersedes ... becomes ✅ Accepted, and 🔄 Superseded by [ADR-0038](adr-0038.md) (2026-06-13) — originally ... becomes 🔄 Superseded by [ADR-0038](adr-0038.md).
Date: Use the exact path found in step 1 to find the commit date when the file was first added, including any filename suffix:
```
git log --follow --diff-filter=A --format=%as -- "docs/adrs/<actual-filename>.md"
```
If the file is untracked (not yet committed), use today's date.
Rebuild the inventory table in docs/adrs/README.md, sorted by ADR number ascending
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

Column	Source	Example
ADR	Filename, linked: `[ADR-NNNN](...)`	`[ADR-0000](adr-0000.md)`
Status	Status label, plus successor link when present	`✅ Accepted` / `🔄 Superseded by [ADR-NNNN](adr-NNNN.md)`
Date	Git first-commit date or today	`2026-02-10`
Title	H1 heading after `ADR-NNNN:`	`Use Architecture Decision Records`

Instructions

Read all adr-*.md files in docs/adrs/
For each file, extract the title from line 1 and status from the Status section
Look up the git creation date for each file
Replace the inventory table section in docs/adrs/README.md with the updated table
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.

Check your setup, free