.claude/skills/lint/SKILL.md
Fix code style issues and ensure linting passes. Use when asked to fix lint errors, formatting issues, or when ktlint or Checkstyle violations are reported.
npx skillsauth add adobe/s3mock lintInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read AGENTS.md (root + relevant module) before making changes.
S3Mock uses two linting tools that run as required CI gates:
| Tool | Target | Config | Auto-fix? |
|------|--------|--------|-----------|
| ktlint | Kotlin source files | .editorconfig | Yes — make format |
| Checkstyle | Java source + XML files | etc/checkstyle.xml | No — fix manually |
Both run automatically as part of the full build (make install).
make format — auto-formats all Kotlin files with ktlint. Fixes the vast majority of Kotlin style issues../mvnw checkstyle:check — reports Checkstyle violations for Java and XML files. Fix violations manually.make sort — sorts POM files with sortpom. Required when any pom.xml was added or modified.make install — confirm all linting gates pass before submitting.make format auto-fixes most issues. Common violations:
To check without modifying files: ./mvnw ktlint:check
Violations must be fixed manually. Common violations (config in etc/checkstyle.xml):
.editorconfig)See docs/JAVA.md for Java style conventions.
AGENTS.md for the files being changedmake format to auto-fix Kotlin style./mvnw checkstyle:check to check Java/XML stylemake sort if any pom.xml was modifieddocs/JAVA.md for Java conventions, docs/KOTLIN.md for Kotlin)make install to confirm all CI gates passdevelopment
Write, update, or fix tests. Use when asked to test code, create test cases, or debug failing tests.
development
Review code changes in PRs or local diffs. Use when asked to review a PR, inspect changes, or provide feedback on code quality.
development
Generate or update project documentation. Use when asked to document code, create docs, explain features, or fix formatting, wording, or style in existing documentation files.
development
Improve code readability, enforce idiomatic conventions, and enhance documentation quality. Use when asked to clean up code, improve naming, add meaningful comments, or align with Kotlin/project idioms.