agentleFS
docxologydocxology/codomyrmex/projects/AGENTS.md

codomyrmex / projects

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Preserve ownership and Git boundaries for integration and example workspaces. - Detect nested .git directories or gitfiles before editing. - Treat every nested repository as an independent worktree with its own status, history, remotes, and agent instructions. - Never fold nested changes into root formatting, cleanup, documentation generation, or release claims. - Run commands from the owning workspace only after reading its README, AGENTS, and package metadata. - Keep root documentation limited to workspace ownership and integration boundaries; detailed behavior…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat every nested repository as an independent worktree with its own status, history, remotes, and agent instructions.

    line 12
  2. Distinctive:

    Never fold nested changes into root formatting, cleanup, documentation generation, or release claims.

    line 14
  3. Distinctive:

    Run commands from the owning workspace only after reading its README, AGENTS, and package metadata.

    line 16
  4. Distinctive:

    Keep root documentation limited to workspace ownership and integration boundaries.

    line 18
  5. Distinctive:

    Do not infer that a historically documented workspace still exists.

    line 20

≈ “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
<!-- agents: curated -->

Agent guidance for project workspaces

Purpose

Preserve ownership and Git boundaries for integration and example workspaces.

Development Guidelines

  • Detect nested .git directories or gitfiles before editing.
  • Treat every nested repository as an independent worktree with its own status, history, remotes, and agent instructions.
  • Never fold nested changes into root formatting, cleanup, documentation generation, or release claims.
  • Run commands from the owning workspace only after reading its README, AGENTS, and package metadata.
  • Keep root documentation limited to workspace ownership and integration boundaries; detailed behavior belongs with the workspace.
  • Do not infer that a historically documented workspace still exists.

Key Files

  • README.md — current workspace inventory and safety boundary
  • SPEC.md — workspace specification
  • test_project/ — current standalone nested worktree

Current scope

The current checkout contains projects/test_project/ as a nested Git worktree. Recheck this fact live before acting.

Navigation

  • Human overview
  • Workspace specification
  • Repository agent contract

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.