agentleFS
hranesshraness/personal-monorepo-template/scripts/AGENTS.md

personal-monorepo-template / scripts

AGENTS.md4 starsChanged 47 days agoMITView on GitHub

The file

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

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

  • 1

    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:

    Keep the serializer stateless and dependency-free.

    line 9
  2. Distinctive:

    Keep documentation checks focused on durable links and required boundaries rather than exact prose or formatting.

    line 12
  3. Distinctive:

    Do not add queue databases, background workers, locks, priority, status, provider delivery, or force-push behavior.

    line 13

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

Contents

  • merge-main.ts – the stateless optimistic serializer for validated direct pushes to origin/main.
  • merge-main.test.ts – argument, environment, safety, and local bare-repository integration coverage.
  • editorial-images-docs.test.ts – deterministic discoverability and contract checks for the optional editorial-image guide.

Guidelines

  • Keep the serializer stateless and dependency-free. Coordinate concurrent submissions through ordinary Git fast-forward behavior, then rebuild on the latest origin/main when another submission wins the race.
  • Resolve submitted refs before integration, reject merge commits, sanitize inherited Git repository overrides, and do all replay and validation work in a task-owned detached temporary worktree.
  • Validate with the frozen Bun install and root check. Push only the exact clean commit that passed validation, disable followed-tag publication, then fetch again and prove it is reachable from origin/main.
  • Keep documentation checks focused on durable links and required boundaries rather than exact prose or formatting.
  • Do not add queue databases, background workers, locks, priority, status, provider delivery, or force-push behavior. Repositories that protect main use pull requests and required checks. Auto-merge can finish validated changes; a provider merge queue is optional when concurrent changes require combined-candidate validation.

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.