auto-mobile
AGENTS.md56 starsChanged 34 days agoApache-2.0View on GitHub
CI runs a Fast Validation job (.github/workflows/pull_request.yml → scripts/all_fast_validate_checks.sh) that gates merges. When you modify any of the files it checks, run the matching validation locally before pushing so the PR check does not fail: Run the whole suite at once with scripts/all_fast_validate_checks.sh (it mirrors the CI job's --only yaml,xml,shellcheck,mkdocs-nav,ktfmt,claude-plugin,codex-skills). Do not add a new standalone validation workflow for something the fast-validation aggregator already covers — extend all_fast_validate_checks.sh and let the existing Fast Validation job pick it up.
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,774 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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- android/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- ios/CLAUDE.mdCLAUDE.md
- auto-mobile-code-reviewSkill
- ci-failure-triageSkill
- github-pr-feedbackSkill
- ios-swift-ciSkill
- node-prepushSkill
- prepush-androidSkill
- shell-prepushSkill
- android-gradlewSkill
- auto-mobile-code-reviewSkill
- bun-tasksSkill
- check-ciSkill
- ci-failure-triageSkill
- dead-codeSkill
- device-session-lifecycleSkill
- fan-out-fan-inSkill
- github-cliSkill
- github-pr-feedbackSkill
- ios-swift-ciSkill
- manual-testSkill
- node-prepushSkill
- observeSkill
- pr-analysisSkill
- prepush-androidSkill
- push-my-prsSkill
- push-prSkill
- researchSkill
- shell-prepushSkill
- ship-issueSkill
- testSkill
- validateSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Run the whole suite at once with scripts/all_fast_validate_checks.sh (it mirrors the CI job's --only …
- Very specific: line 20
Do not add a new standalone validation workflow for something the fast-validation aggregator already covers — extend …
≈ “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.
Files
.github — agent guidance
CI runs a Fast Validation job (.github/workflows/pull_request.yml →
scripts/all_fast_validate_checks.sh) that gates merges. When you modify any of
the files it checks, run the matching validation locally before pushing so the
PR check does not fail:
| If you change… | Run locally |
Test plan YAML (**/test-plans/**/*.yaml) | bun run validate:yaml |
Any CI workflow or files under .github/ | scripts/all_fast_validate_checks.sh |
| XML resources | scripts/all_fast_validate_checks.sh --only xml |
Shell scripts under scripts/ | scripts/all_fast_validate_checks.sh --only shellcheck (or shellcheck) |
| MkDocs nav / docs structure | scripts/all_fast_validate_checks.sh --only mkdocs-nav |
| Kotlin sources | scripts/all_fast_validate_checks.sh --only ktfmt |
Run the whole suite at once with scripts/all_fast_validate_checks.sh (it mirrors
the CI job's --only yaml,xml,shellcheck,mkdocs-nav,ktfmt,claude-plugin,codex-skills).
Do not add a new standalone validation workflow for something the fast-validation
aggregator already covers — extend all_fast_validate_checks.sh and let the
existing Fast Validation job pick it up.
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.

