// 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.
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.
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.
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.
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 | refactor |
| description | 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. |
Use this skill when asked to:
docs/KOTLIN.mdimplement or test skill)Hard constraint: Refactoring must not change observable behavior. If a change would alter behavior, it belongs in the implement skill, not here.
AGENTS.md (root) and the relevant module AGENTS.md.Remove comments that restate what the code does. Add comments only for:
Use KDoc (/** */) for public APIs; inline // comments for rationale only.
If you need a comment to explain what code does, rename instead. See docs/KOTLIN.md for naming conventions.
Apply idioms and anti-pattern fixes from docs/KOTLIN.md: null safety, expression bodies, scope functions, isEmpty()/isNotEmpty(), when expressions, named it alternatives.
Document what, why, and gotchas. Link to AWS S3 API docs where relevant.
make test and/or make integration-tests.INVARIANTS.md.lint skill to fix formatting and verify style gates pass.lint skill)AGENTS.md — DO/DON'T, Code Style sectionINVARIANTS.md — hard constraints (copyright year rule)AGENTS.mddocs/KOTLIN.md — Kotlin idioms, naming conventions, anti-patterns, KDoc guidelines