agentleFS
andrefigueiraandrefigueira/.context/.claude/skills/add-adr/SKILL.md

add-adr

Skill253 starsChanged 11 months agoMITView on GitHub

Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. jjxmonster/skills★ 8same name
    2. nishant-tamilselvan/AEGIS★ 1same name

    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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create a new ADR in .context/decisions/.

    line 8
  2. Very specific:

    Read .context/decisions/README.md for the template and existing ADR numbering

    line 12
  3. Very specific:

    Create .context/decisions/[NNN]-[kebab-case-title].md using the template from README.md

    line 14
  4. Very specific:

    Update .context/decisions/README.md index with the new ADR

    line 16
  5. Distinctive:

    Always document alternatives considered and why they were rejected

    line 24
  6. Distinctive:

    Keep the context section focused on the problem, not the solution

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Create a new ADR in .context/decisions/.

Steps

  1. Read .context/decisions/README.md for the template and existing ADR numbering
  2. Determine the next ADR number (check existing files in .context/decisions/)
  3. Create .context/decisions/[NNN]-[kebab-case-title].md using the template from README.md
  4. Fill in: Title, Status (Proposed), Context, Decision, Consequences, Alternatives Considered
  5. Update .context/decisions/README.md index with the new ADR

Content from user

The user's input describing the decision: $ARGUMENTS

Rules

  • Status should be "Proposed" for new ADRs
  • Always document alternatives considered and why they were rejected
  • Include concrete consequences (both positive and negative)
  • Link to related ADRs if they exist
  • Keep the context section focused on the problem, not the solution

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.