claude-code-java
Overview
Use this skill when a Java project needs reusable coding-agent infrastructure from decebals/claude-code-java. The upstream project is optimized for Claude Code but its conventions are useful for Java agent workflows generally.
Compatibility: Java, Maven, Gradle, testing, refactoring, migration, and Claude Code-style workflows.
Workflow
- Identify the Java version, build tool, framework, module layout, and test stack.
- Inspect upstream instructions before importing conventions into the local repository.
- Keep work tool-native: use Maven or Gradle commands already present in the project.
- For migration tasks, define the source and target versions, dependency changes, and compatibility risks first.
- Validate compile, tests, formatting, and static analysis according to the local project.
Guardrails
- Do not mix Maven and Gradle patterns unless the repository already does.
- Preserve package names, public APIs, serialization contracts, and configuration keys.
- Keep framework-specific assumptions explicit, especially for Spring Boot, Quarkus, Jakarta EE, and Micronaut.
- Treat generated agent instructions as project support material, not application runtime code.
Expected Output
Return Java-focused implementation or migration guidance with build commands, risk notes, and validation evidence.
1---2name: claude-code-java3description: Use claude-code-java for reusable Java project agent infrastructure, conventions, testing, and migration workflows.4license: MIT5---67# claude-code-java89## Overview1011Use this skill when a Java project needs reusable coding-agent infrastructure from [decebals/claude-code-java](https://github.com/decebals/claude-code-java). The upstream project is optimized for Claude Code but its conventions are useful for Java agent workflows generally.1213Compatibility: Java, Maven, Gradle, testing, refactoring, migration, and Claude Code-style workflows.1415## Workflow16171. Identify the Java version, build tool, framework, module layout, and test stack.182. Inspect upstream instructions before importing conventions into the local repository.193. Keep work tool-native: use Maven or Gradle commands already present in the project.204. For migration tasks, define the source and target versions, dependency changes, and compatibility risks first.215. Validate compile, tests, formatting, and static analysis according to the local project.2223## Guardrails2425- Do not mix Maven and Gradle patterns unless the repository already does.26- Preserve package names, public APIs, serialization contracts, and configuration keys.27- Keep framework-specific assumptions explicit, especially for Spring Boot, Quarkus, Jakarta EE, and Micronaut.28- Treat generated agent instructions as project support material, not application runtime code.2930## Expected Output3132Return Java-focused implementation or migration guidance with build commands, risk notes, and validation evidence.
autohandai