agentleFS
Sign inStart free
rvdbreemenrvdbreemen/adr-kit/skills/related/SKILL.md

related

Skill13 starsChanged 4 months agoMITView on GitHub

Show inbound and outbound links for one ADR. Use for related decisions, dependencies, dangling ADR links, supersession, or retirement. Read-only.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. enkerewpo/zoresearch★ 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 repository19 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use $ARGUMENTS as the required ADR id.

    line 13
  2. Very specific:

    Use --adr-dir <path> if the project keeps ADRs somewhere other than docs/adr/.

    line 34
  3. Very specific:

    If the dangling list is non-empty, call it out explicitly: these are references to ADR ids that do not exist in the set.

    line 48
  4. Distinctive:

    Read-only. Never modify ADRs, statuses, or links during a graph load.

    line 59
  5. Very specific:

    If the user wants to act on the graph (supersede, retire), hand off to /adr-kit:supersede or /adr-kit:retire instead of editing here.

    line 64

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

adr-kit related

Reply in the language the user writes in; default to English. Keep command output, identifiers, paths, and ADR file content unchanged.

Use $ARGUMENTS as the required ADR id. Ask for the id when it is empty.

You are running /adr-kit:related. Purpose: show who an ADR points at and who points back at it, before anyone changes its status. This is read-only; it never edits ADRs.

Procedure

  1. Take the ADR id from the argument. If none was given, ask the user which ADR to inspect (id or title fragment is enough; resolve a title fragment by listing docs/adr/ADR-*.md and matching).

  2. Resolve the plugin path and run the bundled graph tool from the project root:

    ADR_KIT="${ADR_KIT_ROOT:-${CLAUDE_PLUGIN_ROOT}}"
[ -n "$ADR_KIT" ] || { echo "adr-kit: plugin root not found; set ADR_KIT_ROOT, or update or reinstall the plugin" >&2; exit 1; }
python "$ADR_KIT/bin/adr-related" ADR-NNN --format json
    • Use --adr-dir <path> if the project keeps ADRs somewhere other than docs/adr/.
    • Exit code 2 means the id is unknown or the directory is missing; relay the stderr message and stop.

  3. Present the graph readably, not as raw JSON:

    • ADR-NNN <title> (status, file path)
    • Outbound: one line per edge, -> ADR-MMM [kind] <title> (<status>). Kinds: related, supersedes, superseded-by, amended-by.
    • Inbound: one line per edge, <- ADR-MMM [kind] <title> (<status>). Inbound also surfaces mention edges: plain ADR-id occurrences outside any declared relationship.
  4. If the dangling list is non-empty, call it out explicitly: these are references to ADR ids that do not exist in the set. Suggest fixing the stale link (typo) or restoring the missing ADR; do not fix it yourself in this skill.
  5. One closing sentence of interpretation: e.g. "Nothing depends on this ADR; superseding it is low-risk" or "Three Accepted ADRs reference this one; superseding it requires updating their Related Decisions."

Boundaries

  • Read-only. Never modify ADRs, statuses, or links during a graph load.
  • Matching is whole-token: ADR-043 is never inferred from ADR-0430. Trust the tool's edges; do not add speculative relationships the files do not state.
  • A mention edge is weak evidence, not a declared dependency. Say so when it is the only inbound edge.
  • If the user wants to act on the graph (supersede, retire), hand off to /adr-kit:supersede or /adr-kit:retire instead of editing here.

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