Spring Boot Skills
Overview
Use this skill when a Spring Boot repository needs production-grade coding-agent guidance from rrezartprebreza/spring-boot-skills. The upstream repository provides Claude Code skills for Spring Boot developers.
Compatibility: Spring Boot, Java, Maven, Gradle, testing, migration, and production operations.
Workflow
- Identify the Spring Boot version, Java version, dependency management style, profiles, and test strategy.
- Check upstream skill instructions for the relevant concern: controllers, services, data access, security, testing, migration, or observability.
- Keep changes aligned with existing architecture: layered services, hexagonal boundaries, or domain modules.
- For migrations, plan dependency and configuration changes before touching application logic.
- Validate with repository-native Maven or Gradle commands and targeted integration tests where available.
Guardrails
- Do not introduce new frameworks or starters without a concrete need.
- Preserve configuration property names, profile behavior, database migrations, and API contracts.
- Treat generated code that affects transactions, security, or data access as high review priority.
- Make actuator, logging, and observability changes explicit.
Expected Output
Return a Spring Boot implementation or migration plan with affected modules, commands, tests, and operational notes.
1---2name: spring-boot-skills3description: Use spring-boot-skills for production-grade Spring Boot agent guidance, modernization, testing, and operations.4license: MIT5---67# Spring Boot Skills89## Overview1011Use this skill when a Spring Boot repository needs production-grade coding-agent guidance from [rrezartprebreza/spring-boot-skills](https://github.com/rrezartprebreza/spring-boot-skills). The upstream repository provides Claude Code skills for Spring Boot developers.1213Compatibility: Spring Boot, Java, Maven, Gradle, testing, migration, and production operations.1415## Workflow16171. Identify the Spring Boot version, Java version, dependency management style, profiles, and test strategy.182. Check upstream skill instructions for the relevant concern: controllers, services, data access, security, testing, migration, or observability.193. Keep changes aligned with existing architecture: layered services, hexagonal boundaries, or domain modules.204. For migrations, plan dependency and configuration changes before touching application logic.215. Validate with repository-native Maven or Gradle commands and targeted integration tests where available.2223## Guardrails2425- Do not introduce new frameworks or starters without a concrete need.26- Preserve configuration property names, profile behavior, database migrations, and API contracts.27- Treat generated code that affects transactions, security, or data access as high review priority.28- Make actuator, logging, and observability changes explicit.2930## Expected Output3132Return a Spring Boot implementation or migration plan with affected modules, commands, tests, and operational notes.
autohandai