claude-bridge
CLAUDE.md1 starsChanged 33 days agoApache-2.0View on GitHub
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-reviewSkill
- rescueSkill
- reviewSkill
The file
We split this CLAUDE.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
- Distinctive: line 5
Write project docs, commit subjects, commit bodies, and release notes in English.
- Distinctive: line 6
Keep bullet lists compact: use one to four bullets per list and do not put blank lines between bullet items.
- Distinctive: line 7
Keep README structure, installation flow, and terminology consistent across Claude Bridge and Antigravity Bridge.
- Distinctive: line 11
Use concise English commit subjects.
- Distinctive: line 12
Use commit bodies only when useful.
- Distinctive: line 13
Before pushing, verify git diff --check and inspect commit messages for non-ASCII text and repeated blank lines.
- Very specific: line 18
If browser or web search tools hit certificate errors, first try a CLI fallback such as curl-cffi get https://www.naver.com.
- Distinctive: line 19
If a required URL still times out after that fallback, treat a corporate Wi-Fi firewall as a possible cause and report only that …
- Distinctive: line 23
Do not stage unrelated local changes.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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.
Files
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 --checkand inspect commit messages for non-ASCII text and repeated blank lines. - For release tags, create or move
v1.0.0at 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.
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
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.

