agentleFS
pdparchitectpdparchitect/noodle/AGENTS.md

noodle

AGENTS.md259 starsChanged 35 days agoApache-2.0View on GitHub

Assume that multiple ai agents are editing this project. Don't get surprised. Committing is prohibited. Never commit, amend, push, tag or rewrite history unless the user explicitly asks for it in that message. A documented process, a finished task or an earlier approval is not permission. Stage changes only when asked. Keep CHANGELOG.md current as part of every user-visible change. Add a concise entry under the appropriate heading in Unreleased in the same change; do not wait for release preparation…

The file

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

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

  • 3

    Very specific

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

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

    Keep CHANGELOG.md current as part of every user-visible change.

    line 13
  2. Very specific:

    No changelog entries for website/ changes.

    line 15
  3. Distinctive:

    Do not publish a release unless the user explicitly asks.

    line 17
  4. Very specific:

    Run local builds and tests at low priority so the laptop stays usable: prefix swift build, swift test and xcodebuild with …

    line 26

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

Concurrent edits

Assume that multiple ai agents are editing this project. Don't get surprised.

Commits

Committing is prohibited. Never commit, amend, push, tag or rewrite history unless the user explicitly asks for it in that message. A documented process, a finished task or an earlier approval is not permission. Stage changes only when asked.

Release notes

Keep CHANGELOG.md current as part of every user-visible change. Add a concise entry under the appropriate heading in Unreleased in the same change; do not wait for release preparation to reconstruct it later.

No changelog entries for website/ changes; they would trigger rebuilds.

Do not publish a release unless the user explicitly asks.

Documentation

READMEs and docs/ are for people using the apps. Code is documented only in its own comments; follow the no-code-docs skill.

Builds on this Mac

Run local builds and tests at low priority so the laptop stays usable: prefix swift build, swift test and xcodebuild with scripts/build-priority.sh (the repository's scripts already do). CI runs at full speed.

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.