agentleFS
Sign inStart free
dydtjr1128dydtjr1128/claude-bridge/AGENTS.md

claude-bridge

AGENTS.md1 starsChanged 33 days agoApache-2.0View 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,542 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 repository4 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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
  1. Distinctive:

    Write project docs, commit subjects, commit bodies, and release notes in English.

    line 5
  2. Distinctive:

    Keep bullet lists compact: use one to four bullets per list and do not put blank lines between bullet items.

    line 6
  3. Distinctive:

    Keep README structure, installation flow, and terminology consistent across Claude Bridge and Antigravity Bridge.

    line 7
  4. Distinctive:

    Use concise English commit subjects.

    line 11
  5. Distinctive:

    Use commit bodies only when useful.

    line 12
  6. Distinctive:

    Before pushing, verify git diff --check and inspect commit messages for non-ASCII text and repeated blank lines.

    line 13
  7. Very specific:

    If browser or web search tools hit certificate errors, first try a CLI fallback such as curl-cffi get https://www.naver.com.

    line 18
  8. Distinctive:

    If a required URL still times out after that fallback, treat a corporate Wi-Fi firewall as a possible cause and report only that …

    line 19
  9. Distinctive:

    Do not stage unrelated local changes.

    line 23

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

Repository Instructions

Language And Formatting

  • Write project docs, commit subjects, commit bodies, and release notes in English.
  • Keep bullet lists compact: use one to four bullets per list and do not put blank lines between bullet items.
  • Keep README structure, installation flow, and terminology consistent across Claude Bridge and Antigravity Bridge.

Git And Release

  • Use concise English commit subjects.
  • Use commit bodies only when useful; if used, keep bullet lines adjacent with no blank lines between them.
  • Before pushing, verify git diff --check and inspect commit messages for non-ASCII text and repeated blank lines.
  • For release tags, create or move v1.0.0 at the current release commit and push the tag when requested.

Web Access

  • If browser or web search tools hit certificate errors, first try a CLI fallback such as curl-cffi get https://www.naver.com.
  • If a required URL still times out after that fallback, treat a corporate Wi-Fi firewall as a possible cause and report only that possibility.

Worktree Safety

  • Do not stage unrelated local changes; commit only the requested files.
  • Preserve user edits in the worktree unless explicitly asked to change them.

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