java-coding-standards

Enforce Java 17+ coding standards for Spring Boot services.

23|7|Updated Feb 22, 2026

Search Tags:#best practices #clean code #coding standards #maintainability #java #spring boot

Ready to run

npx skills add https://github.com/hzy970907/fish-claude-code --skill java-coding-standards-hzy970907

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: java-coding-standards
Source: https://github.com/hzy970907/fish-claude-code/tree/main/skills/java-coding-standards
Command: npx skills add https://github.com/hzy970907/fish-claude-code --skill java-coding-standards-hzy970907

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces consistent, readable, and maintainable Java code standards, preventing common code smells and ensuring adherence to best practices in Spring Boot projects.

Core Features & Use Cases

Standardized Naming Conventions: Ensures consistent naming for classes, methods, and constants.
Immutability Enforcement: Promotes the use of immutable objects and records.
Effective Optional and Stream Usage: Guides developers on best practices for Optional and Java Streams.
Exception Handling: Provides guidelines for robust exception management.
Project Structure: Recommends a clear and organized project layout.
Use Case: When writing new Java code or reviewing existing code, this Skill acts as a guide to ensure the code is clean, maintainable, and follows established best practices, reducing technical debt and improving collaboration.

Quick Start

Apply the java-coding-standards skill to review the current Java code for adherence to best practices.

Frequently Asked Questions about java-coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are the best practices for writing clean Java code in Spring Boot?▼

Clean Java code in Spring Boot requires standardized naming conventions, immutability enforcement using records, effective Optional and Stream usage, and robust exception handling to improve maintainability.

How do I enforce Java 17 coding standards for my current project?▼

Enforce Java 17 coding standards by applying guidelines for project structure, null handling, logging, and testing expectations with JUnit 5 and Mockito to ensure code clarity.

Does this coding standard support testing with JUnit 5 and Mockito?▼

Yes, the coding standards include specific guidelines for testing expectations using JUnit 5 and Mockito to validate Spring Boot services and ensure robust exception management.

What's the best way to handle Optional and Java Streams in Spring Boot?▼

Handle Optional and Java Streams by following established guidelines that promote code clarity, prevent magic numbers, and ensure maintainability across your Spring Boot project structure.

How do I prevent common code smells like magic numbers and deep nesting in Java?▼

Prevent code smells like magic numbers and deep nesting in Java by enforcing immutability, utilizing specific logging and null handling guidelines, and adhering to strict naming conventions for constants.