agentleFS
Sign inStart free
docxologydocxology/codomyrmex/tests/AGENTS.md

codomyrmex / tests

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

- Follow the repository zero-mock policy. Use real classes, files, subprocesses, temporary directories, and local services. - Narrow environment, cwd, and temporary-path isolation is permitted as described in SPEC.md. - Test public behavior and failure receipts, not implementation trivia. - Add negative controls for path traversal, tampering, absent evidence, no-mode execution, dry-run byte preservation, and optional dependencies when relevant. - Never write to real user configuration, credentials, home directories, external services, or publication targets. - Keep tests deterministic under the…

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the repository zero-mock policy.

    line 7
  2. Distinctive:

    Test public behavior and failure receipts, not implementation trivia.

    line 11
  3. Distinctive:

    Add negative controls for path traversal, tampering, absent evidence, no-mode execution, dry-run byte preservation, and optional …

    line 12
  4. Common:

    Never write to real user configuration, credentials, home directories, external services, or publication targets.

    line 15
  5. Distinctive:

    Keep tests deterministic under the fixed-epoch or seeded contracts used by the owning module.

    line 17
  6. Distinctive:

    Do not weaken or delete a failing test merely to make a gate green.

    line 19
  7. Distinctive:

    Update the nearest README/SPEC when test scope or invocation changes.

    line 21
  8. Distinctive:

    Run the narrowest relevant test first:

    line 25

≈ “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
<!-- agents: curated -->

Agent guidance for tests

Operating contract

  • Follow the repository zero-mock policy. Use real classes, files, subprocesses, temporary directories, and local services.
  • Narrow environment, cwd, and temporary-path isolation is permitted as described in SPEC.md.
  • Test public behavior and failure receipts, not implementation trivia.
  • Add negative controls for path traversal, tampering, absent evidence, no-mode execution, dry-run byte preservation, and optional dependencies when relevant.
  • Never write to real user configuration, credentials, home directories, external services, or publication targets.
  • Keep tests deterministic under the fixed-epoch or seeded contracts used by the owning module.
  • Do not weaken or delete a failing test merely to make a gate green; establish whether implementation, expectation, or environment is wrong.
  • Update the nearest README/SPEC when test scope or invocation changes.

Validation

Run the narrowest relevant test first:

uv run --locked pytest -q tests/unit/<module>

Then run formatting, lint, typing, and the full coverage gate appropriate to the change. make test is the authoritative 60% coverage invocation.

Navigation

  • Human overview
  • Testing specification
  • Running tests
  • Repository agent contract

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