adobe/refactor
.claude/skills/refactor/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add adobe/s3mock refactorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 5:45 AM40.2s1 file scanned
SKILL.md
- name:
- refactor
- description:
- 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.
Refactor Skill — S3Mock
Read AGENTS.md (root + relevant module) before making changes — especially DO/DON'T and Code Style sections. Refactoring must not change behavior — only readability and style.
Pre-Flight
- Understand the code's purpose — read callers and tests first
- Confirm changes are purely cosmetic (no behavior changes)
- Check existing test coverage
Guiding Principles
Comments Explain "Why", Never "What"
Remove comments that restate code. Add comments for why a decision was made, edge cases, or non-obvious S3 semantics. Reference AWS S3 API docs or GitHub issues for workarounds. Use KDoc (/** */) for public APIs; inline comments (//) for rationale.
Meaningful Naming Over Comments
If you need a comment to explain what code does, rename instead. See docs/KOTLIN.md for naming conventions.
Idiomatic Kotlin & Common Anti-Patterns
See docs/KOTLIN.md for the full list of Kotlin idioms, common anti-patterns and their fixes, and scope function guidance.
KDoc for Public APIs
Document what, why, and gotchas. Link to AWS API docs where relevant. See docs/KOTLIN.md for KDoc conventions.
Checklist
- [ ] Verify no behavior changes — run tests
- [ ] Update copyright year to
2017-<current year>in the header of every file you modify - [ ] Invoke the
lintskill to fix formatting and verify style gates pass - [ ] Ensure comments explain why, not what
- [ ] Add KDoc for all public APIs
- [ ] Use self-documenting names
Related Skills
adobe/test
development
VerifiedTrustedCommunity
Write, update, or fix tests. Use when asked to test code, create test cases, or debug failing tests.
1,084SKILL.mdUpdated Mar 27, 2026
adobe/review
development
VerifiedTrustedCommunity
Review code changes in PRs or local diffs. Use when asked to review a PR, inspect changes, or provide feedback on code quality.
1,084SKILL.mdUpdated Mar 27, 2026
adobe/lint
development
VerifiedTrustedCommunity
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.
1,084SKILL.mdUpdated Mar 27, 2026
adobe/document
development
VerifiedTrustedCommunity
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.
1,084SKILL.mdUpdated Mar 27, 2026