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

implement

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

Implement features, fix bugs, and modify production source code in S3Mock. Use when asked to add functionality, change behavior, or modify source files in server/, integration-tests/, or testsupport/. Not for documentation-only or test-only changes. Orchestrates lint, test, and document skills as part of the complete workflow.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 0

    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 for new functionality, bug fixes, or behavior changes in server/, integration-tests/, or testsupport/.

    line 10
  2. Very specific:

    Read root AGENTS.md and the relevant module AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.md).

    line 14
  3. Very specific:

    If nearby code would benefit from cleanup before adding new code, invoke the refactor skill first.

    line 17
  4. Very specific:

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

    line 22
  5. Very specific:

    Docker fails: use make skip-docker to isolate the build from Docker issues.

    line 39

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

Implementation Skill

Entry Criteria

Use for new functionality, bug fixes, or behavior changes in server/, integration-tests/, or testsupport/. Not for test-only or documentation-only changes — use the test or document skill instead.

Before Starting

  1. Read root AGENTS.md and the relevant module AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.md).
  2. For a new S3 operation, verify element names and behavior against the AWS S3 API docs.
  3. Review existing similar implementations for patterns to follow.
  4. If nearby code would benefit from cleanup before adding new code, invoke the refactor skill first.

Execution Steps

  1. For a new S3 operation, follow server/AGENTS.md § Implementation Flow (DTO → Store → Service → Controller → IT) — do not skip layers or add logic in the wrong layer.
  2. Update the copyright year in every modified file (INVARIANTS.md).
  3. Invoke the lint skill.
  4. Invoke the test skill to add or update unit and integration tests.
  5. Invoke the document skill to update CHANGELOG.md, README.md, and AGENTS.md where applicable.

Completion Criteria

  • Code compiles (make skip-docker)
  • Unit tests pass (make test); integration tests pass (make integration-tests)
  • Lint gates pass (via lint skill)
  • Copyright year updated in every modified file
  • Tests added/updated (via test skill); docs updated (via document skill)

Troubleshooting

  • Build fails: confirm JDK 25 is active; run make format and fix remaining lint errors.
  • XML test failures: a compile check is not sufficient (INVARIANTS.md) — run integration tests to confirm serialized output.
  • Docker fails: use make skip-docker to isolate the build from Docker issues.

Resources

  • AGENTS.md, INVARIANTS.md
  • Relevant module AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.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 versions191 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 191

    1. mattpocock/skills★ 309ksame name
    2. QuivrHQ/quivr★ 40ksame name
    3. foambubble/foam★ 17ksame name
    4. formbricks/formbricks★ 13ksame name
    5. ArcReel/ArcReel★ 6ksame name
    6. vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
    7. fallow-rs/fallow★ 5.3ksame name
    8. withcoral/coral★ 4.9ksame name
    9. bestofjs/bestofjs★ 3.1ksame name
    10. meta-pytorch/OpenEnv★ 2.8ksame name

    181 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 setup-ts-deep-modules, ask-matt 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.
    • liufeng1976Skill

      setup-ts-deep-modules

      Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

      Also in 33 projects that use this

    • GoogleSkill

      ask-matt

      Ask which skill or flow fits your situation. A router over the skills in this repo.

      Also in 79 projects that use this

    • AWSSkill

      to-questionnaire

      Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

      Also in 76 projects that use this

    • GoogleSkill

      to-tickets

      Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

      Also in 138 projects that use this

    • RoentekSkill

      loop-me

      Grill me about specs for the workflows I want to build, within this workspace.

      Also in 42 projects that use this

    • ryotaroh180105Skill

      claude-handoff

      Hand the current conversation off to a fresh background agent that picks up the work immediately.

      Also in 34 projects that use this

    • +2 more from google
  • 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.