springboot-verification

Runs build, static analysis, tests, security scans, and diff review for Spring Boot projects.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill springboot-verification-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: springboot-verification
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/springboot-verification
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill springboot-verification-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Spring Boot changes often ship with hidden build failures, low test coverage, or security issues discovered too late. This Skill enforces a structured verification loop before PRs and deployments so defects are caught early. ## Core Features & Use Cases - Phased Verification Pipeline: Runs build, static analysis (SpotBugs, PMD, Checkstyle), tests with JaCoCo coverage, OWASP dependency checks, secrets scanning, and diff review in sequence. - Test Patterns Included: Provides ready-to-use examples for unit tests with Mockito, integration tests with Testcontainers, and API tests with MockMvc. - Use Case: Before opening a pull request for a Spring Boot service, run the full loop to confirm the build passes, coverage meets the 80% threshold, no CVEs or hardcoded secrets exist, and produce a READY/NOT READY verification report. ## Quick Start Run the Spring Boot verification loop on my project and report build, test coverage, and security scan results before I open a pull request.

Frequently Asked Questions about springboot-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Spring Boot project before a pull request?▼

Run a phased loop: build with mvn clean verify, static analysis with SpotBugs, PMD, and Checkstyle, tests with JaCoCo coverage, OWASP dependency checks, and a final git diff review. Stop and fix at the first failing phase.

How to check test coverage in a Spring Boot Maven project?▼

Run mvn test followed by mvn jacoco:report to generate a coverage report, then verify line and branch coverage meets your threshold, typically 80 percent. Gradle projects use ./gradlew test jacocoTestReport instead.

Should I use Testcontainers or H2 for Spring Boot integration tests?▼

Testcontainers runs tests against a real database like PostgreSQL in a Docker container, matching production behavior more closely than H2. Use @DynamicPropertySource to inject the container's JDBC URL, username, and password into the Spring context.

How do I scan Spring Boot dependencies for known vulnerabilities?▼

Run mvn org.owasp:dependency-check-maven:check for Maven or ./gradlew dependencyCheckAnalyze for Gradle to detect CVEs in dependencies. Also grep the source for hardcoded passwords, API keys, and secrets.

Why does the verification loop stop when the build fails?▼

Later phases like static analysis and tests depend on a successful compilation, so running them on a broken build wastes time and produces misleading results. Fix build errors first, then proceed through the remaining phases in order.