agentleFS
adobeadobe/S3Mock/.agents/skills/test/SKILL.md

test

Skill1.2k starsChanged 3 months agoApache-2.0View on GitHub

Write, update, and fix tests in S3Mock. Use when asked to add test coverage, create test cases, fix failing tests, or verify test correctness. Covers unit tests (*Test.kt in server/), controller slice tests (@WebMvcTest), and integration tests (*IT.kt in integration-tests/ against a live Docker container).

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 144 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use to add/update unit tests (*Test.kt) or integration tests (*IT.kt), fix failing tests, or verify test coverage.

    line 10
  2. Distinctive:

    Read root AGENTS.md, the relevant module AGENTS.md, and docs/TESTING.md for base classes, conventions, and running commands.

    line 14
  3. Very specific:

    If existing tests have structural problems (poor naming, shared state, weak assertions), invoke the refactor skill first.

    line 15
  4. Very specific:

    Write tests following docs/TESTING.md conventions (naming, structure, assertions, independence).

    line 20
  5. Very specific:

    Update the copyright year in every modified file (INVARIANTS.md).

    line 22
  6. Very specific:

    Run make test (unit) or make integration-tests (integration) to verify locally.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 144 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

Test Skill

Entry Criteria

Use to add/update unit tests (*Test.kt) or integration tests (*IT.kt), fix failing tests, or verify test coverage.

Before Starting

  1. Read root AGENTS.md, the relevant module AGENTS.md, and docs/TESTING.md for base classes, conventions, and running commands.
  2. If existing tests have structural problems (poor naming, shared state, weak assertions), invoke the refactor skill first.

Execution Steps

  1. Select the base class per docs/TESTING.md § Unit Tests, or S3TestBase per integration-tests/AGENTS.md for integration tests.
  2. Write tests following docs/TESTING.md conventions (naming, structure, assertions, independence).
  3. Cover both success and failure/error paths.
  4. Update the copyright year in every modified file (INVARIANTS.md).
  5. Invoke the lint skill.
  6. Run make test (unit) or make integration-tests (integration) to verify locally.

Completion Criteria

  • All new/changed code paths covered, including failure cases
  • Correct base class and conventions used (per docs/TESTING.md)
  • Tests pass locally
  • Copyright year updated in every modified file
  • Lint gates pass (via lint skill)

Resources

  • AGENTS.md, INVARIANTS.md
  • Relevant module AGENTS.md (server/AGENTS.md or integration-tests/AGENTS.md)
  • docs/TESTING.md, docs/KOTLIN.md

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 3 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the adobe/S3Mock repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about adobe/S3Mock

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub, Stack Overflow and Hacker News (50 times).

On GitHub · 46

41 more on GitHub

On Hacker News · 1

  • Other versions169 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 169

    1. react/react★ 252ksame name
    2. facebook/react★ 252ksame name
    3. apache/skywalking★ 25ksame name
    4. livewire/livewire★ 24ksame name
    5. NVIDIA/TensorRT★ 13ksame name
    6. FalkorDB/FalkorDB★ 11ksame name
    7. FastLED/FastLED★ 7.5ksame name
    8. fleetdm/fleet★ 7.1ksame name
    9. parcadei/Continuous-Claude★ 3.9ksame name
    10. parcadei/Continuous-Claude-v2★ 3.9ksame name

    159 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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.
  • In this repository10 other files it gives its agents.

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.