agentleFS
kaeawckaeawc/auto-mobile/.github/AGENTS.md

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.

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
  1. Very specific:

    Run the whole suite at once with scripts/all_fast_validate_checks.sh (it mirrors the CI job's --only …

    line 17
  2. Very specific:

    Do not add a new standalone validation workflow for something the fast-validation aggregator already covers — extend …

    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

.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 resourcesscripts/all_fast_validate_checks.sh --only xml
Shell scripts under scripts/scripts/all_fast_validate_checks.sh --only shellcheck (or shellcheck)
MkDocs nav / docs structurescripts/all_fast_validate_checks.sh --only mkdocs-nav
Kotlin sourcesscripts/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.

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.