// 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.
Generate and update S3Mock project documentation. Use when asked to document code, update CHANGELOG.md, update README.md, update AGENTS.md files, or fix formatting, wording, or style in any existing documentation file. Also invoked at the end of the implement skill workflow.
Fix code style issues and ensure linting CI gates pass in S3Mock. Use when ktlint or Checkstyle violations are reported, when asked to fix formatting, or as a required final step after any code change. Runs ktlint for Kotlin source files and Checkstyle for Java and XML files.
Improve code readability, enforce idiomatic Kotlin conventions, and enhance documentation quality in S3Mock without changing behavior. Use when asked to clean up code, improve naming, add KDoc, or align with Kotlin/project idioms. Also invoked by the implement and test skills before adding new code to messy areas.
Review code changes in pull requests or local diffs for S3Mock. Use when asked to review a PR, inspect changes, or provide structured feedback on correctness, conventions, test quality, and documentation. Outputs findings structured as Must fix / Should fix / Nit.
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).
| name | implement |
| description | 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. |
Use this skill when asked to:
server/, integration-tests/, or testsupport/Not for test-only or documentation-only changes — use the test or document skill instead.
AGENTS.md (root) and the relevant module AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.md).refactor skill first.Follow this order exactly — do not skip layers or add logic in the wrong layer:
server/.../dto/): Create data classes with Jackson XML annotations. Verify element and attribute names match the AWS S3 API specification exactly — see INVARIANTS.md. A compile check is not sufficient; run integration tests to verify serialized output.server/.../store/): Add filesystem operations. Follow existing patterns for binary data and metadata JSON.server/.../service/): Add business logic and validation. Throw S3Exception constants only — see INVARIANTS.md.server/.../controller/): Add HTTP mapping only. Delegate all logic to services. Controllers never catch exceptions — see INVARIANTS.md.2017-<current year> in the license header of every file you modify — see INVARIANTS.md.lint skill after implementation to fix formatting and verify style gates.test skill to add or update unit and integration tests.document skill to update CHANGELOG.md, README.md, and AGENTS.md where applicable.make skip-docker)make test)make integration-tests)lint skill)test skill)document skill)make format and fix remaining lint errors.make skip-docker to isolate the build from Docker issues.AGENTS.md — architecture, DO/DON'T, build commandsINVARIANTS.md — hard constraints (copyright, SDK version, XML naming, layering rules)AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.md)docs/KOTLIN.md — Kotlin idioms and naming conventionsdocs/SPRING.md — Spring Boot patterns, DI, exception handling