This collection provides structured guidance for Java backend engineers managing complex codebases. It focuses on the technical rigor required to maintain long-term project health, from evaluating module boundaries and dependency directions to enforcing clean code principles like DRY and KISS.
The tools assist in the critical phases of the development lifecycle, ensuring REST API contracts maintain backward compatibility and that legacy refactoring reduces deep nesting and method length.
Follow the documented setup, then try a first task.
Installs: Complete claude-code-java skills collection, installed as skills only in the current project.
Run from: The root of the project where the skills should be installed.
Run this command in a terminal from the target project's root directory.
npx skills@latest add decebals/claude-code-java
Installs: Complete claude-code-java skills collection plus CLAUDE.md generation, MCP configuration, and project settings. · Claude Code
Platform: Unix-like terminal shell supporting ~ paths, chmod, shell scripts, and *.sh glob expansion.
Run this complete command block in a terminal to clone the workspace, enter it, and make its scripts executable.
git clone https://github.com/decebals/claude-code-java.git ~/projects/claude-code-java cd ~/projects/claude-code-java chmod +x scripts/*.sh
From the cloned workspace, run the setup script in a terminal. Replace ~/projects/your-java-project with the path to the Java project being configured; the documented placeholder is preserved in the command.
./scripts/setup-project.sh ~/projects/your-java-project
In a terminal, change into the configured Java project and start Claude Code. Replace ~/projects/your-java-project with the same Java-project path used during setup; the documented placeholder is preserved in the command.
cd ~/projects/your-java-project claude
Once inside the Claude Code agent session, allow skills to load automatically from context or invoke a documented skill directly by entering `/git-commit` or `/java-code-review`.
Uses java-code-review
Use the java-code-review skill to review the Java code at [path/to/file-or-feature]. Perform a quick scan and checklist pass, then report findings by severity with line references and suggested improvements. Do not modify any files.
Uses architecture-review
Use the architecture-review skill to review [path/to/project-or-module]. Focus on package organization, dependency direction, layering, and module boundaries, then provide prioritized recommendations. Do not modify any files.
Uses changelog-generator
Use the changelog-generator skill in the Git repository at [path/to/repository] to preview unreleased changes from its git commits. Detect the existing versioning and changelog conventions, and return a draft only without updating any files.
Claude