java-clean-codelisted

# Skill: java-clean-code ## Activation Contract Use this skill when reviewing or improving Java code for readability, naming, structure, idiomatic style, method/class size, comments, constants, and maintainability. Do **not** use this skill for non-Java code, test-writing, deep refactoring catalogs, security-only review, performance tuning, or framework-specific configuration. ## Responsibility This skill teaches Java clean-code review and improvement. It does not call other skills, introduce new architecture by default, or change behavior unless explicitly requested. ## Required Context - Java version when known. - Code under review or the file/class purpose. - Existing team style if it differs from common Java conventions. - Whether public API compatibility must be preserved. ## Context Budget - Keep this `SKILL.md` focused on the review workflow. - Use `references/java-clean-code-guidance.md` for naming and official-source notes. ## Hard Rules - Preserve behavior unless the user asks for behavior change. - Prefer expressive names over comments that explain unclear code. - Use Java naming conventions: classes as nouns, methods as verbs, variables meaningful, constants uppercase with underscores. - Do not create `Utils`/`Helper` buckets unless responsibility is explicit and cohesive. - Avoid premature abstraction; first make the current intent obvious. - Treat Oracle Code Conventions as archived historical guidance; prefer modern Java practices where they differ.