spring-boot-verificationlisted
Install: claude install-skill rrezartprebreza/spring-boot-skills
# Spring Boot 3 Verification
Produce an evidence-backed readiness report, not a blanket "production-ready" verdict.
Inspect the repository's build files, wrappers, CI and contribution instructions first.
## Select the actual checks
- Establish the effective Boot 3 version, JDK used by Maven/Gradle, toolchain and target
release. A JDK installed elsewhere does not fix the JVM running the build.
- Preserve the build tool, profiles, module boundaries and existing quality thresholds.
Check wrapper provenance before execution; build scripts and plugins execute code.
Derive mandatory gates from repository/CI policy; disclose ambiguity instead of inventing gates.
- List the checks and their external requirements before running. Use disposable dependencies.
A verification request does not authorize production access, credential uploads or deployment.
- Use the project's configured wrapper and CI commands. For Maven, `./mvnw verify`
runs the lifecycle through integration-test verification **only if** Failsafe is bound.
Do not stop at `integration-test`: teardown and failure verification occur later.
- For Gradle, inspect configured tasks and their dependencies. `./gradlew check` does not
guarantee a separately registered `integrationTest` task runs; invoke it only if it exists
and is not already connected. Preserve Kotlin/Groovy DSL and version catalogs.
- Run configured lint/static analysis and coverage gates, not arbitrary plugin goals.
A JaCoCo report is not an