agentleFS
Sign inStart free
kaeawckaeawc/auto-mobile/skills/test/SKILL.md

test

Skill56 starsChanged 34 days agoApache-2.0View on GitHub

Use this workflow skill for running tests only: choose the narrowest relevant test command first and keep test runs fast and actionable; prefer validate when the user wants broader non-test checks too.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Use the smallest test command that answers the user’s question.

    line 8
  2. Very specific:

    Prefer validate when lint, build, formatting, or other non-test checks are part of the request.

    line 11
  3. Distinctive:

    Prefer targeted tests before full suites.

    line 16
  4. Distinctive:

    Keep unit tests fast and deterministic.

    line 32
  5. Distinctive:

    Use interfaces, fakes, and fake timers when adding or fixing tests.

    line 33
  6. Distinctive:

    Do not accept a failing test as an allowable outcome.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “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
SKILL.md

Run Tests

Use the smallest test command that answers the user’s question.

  • This skill is test-focused.
  • Prefer validate when lint, build, formatting, or other non-test checks are part of the request.

Workflow

  1. Determine the scope from the changed files or the user request.
  2. Prefer targeted tests before full suites.
  3. For TypeScript, use bun test <file> or bun test --bail before bun test when narrowing failures.
  4. For Android or iOS, run only the relevant platform test command.
  5. Save verbose logs to scratch/ when needed and summarize failures with file names and root causes.

Repo Validation Mapping

  • TypeScript all tests: bun test
  • Single TypeScript file: bun test <file>
  • Timing budget check: bash scripts/validate-bun-test-timings.sh --run-unit-lane, or pass an existing focused JUnit XML report to measure it directly
  • Android: (cd android && ./gradlew test) or a narrower task
  • iOS Swift package tests: bash scripts/ios/swift-test.sh
  • Local component or integration flows: prefer a purpose-built script in scripts/

Test Quality Rules

  • Keep unit tests fast and deterministic.
  • Use interfaces, fakes, and fake timers when adding or fixing tests.
  • Do not accept a failing test as an allowable outcome.

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