agentleFS
Sign inStart free
PapiScholzPapiScholz/roadmapsmith/.claude/agents.md

roadmapsmith

AGENTS.md1 starsChanged 5 months agoMITView on GitHub

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository5 other files it gives its agents.

The file

We split this agents.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Write release notes to a temp file.

    line 3
  2. Very specific:

    After every PR merge, delete the local fix branch with git branch -D <branch> and pull main (squash merges require -D, not -d).

    line 4
  3. Distinctive:

    When changing the action gate, grep test fixtures for action-verb task texts first.

    line 6
  4. Distinctive:

    When removing CLI commands, update functional-smoke gate checks in the same commit.

    line 7
  5. Very specific:

    Run node scripts/run-tests.js, not node --test, before pushing.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
agents.md

Rules

  • Write release notes to a temp file; never inline markdown in --notes.
  • After every PR merge, delete the local fix branch with git branch -D <branch> and pull main (squash merges require -D, not -d).
  • Token overlap cannot override a human warning; require Evidence line or test.
  • When changing the action gate, grep test fixtures for action-verb task texts first.
  • When removing CLI commands, update functional-smoke gate checks in the same commit.
  • Run node scripts/run-tests.js, not node --test, before pushing.

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