springboot-verification

Spring Boot verification automates end-to-end checks including builds, static analysis, tests with coverage, security scans, and diff review. Run the verification loop in your CI pipeline for Maven or Gradle projects to enforce quality gates before PR merge, delivering a ready/not-ready status.

Yes, Spring Boot verification supports both Maven and Gradle-based projects. For Maven, use `mvn clean verify`; for Gradle, use `./gradlew clean build`. The Skill targets either build system and integrates into CI pipelines seamlessly.

Spring Boot verification enforces build success, static analysis plugins, test execution with coverage reporting, dependency and security scanning for CVEs, code lint and format checks, and diff review gating. All checks must pass before marking changes ready for merge.

Yes, Spring Boot verification includes dependency and security scanning to identify CVEs and vulnerabilities before release. Security checks run as part of the end-to-end verification loop alongside build, tests, and static analysis.

Spring Boot verification runs tests with coverage enforcement and reporting built into the verification loop. Configure coverage thresholds in your build; the Skill gates PR merge until coverage targets are met.

Spring Boot verification includes diff review gating as part of its end-to-end checks. Changes are reviewed before merge, ensuring code quality alongside build, test, security, and static analysis verification.