Springboot Verification
Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency and secret scans, and diff review — producing a pass/fail readiness report. Use when preparing a Spring Boot pull request, validating coverage thresholds, or running pre-deploy verification.
Get the complete skill folder, including its scripts and reference files.
·
When to use this skill
Use Springboot Verification when an AI agent needs a reusable SKILL.md workflow for this job: Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency and secret scans, and diff review — producing a pass/fail readiness report. Use when preparing a Spring Boot pull request, validating coverage thresholds, or running pre-deploy verification.
When not to use it
Skip Springboot Verification when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/springboot-verification # Save SKILL.md to ~/.claude/skills/springboot-verification/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/springboot-verification/SKILL.md. For a shared project, commit the folder at .claude/skills/springboot-verification/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Springboot Verification skill for this task: Use Springboot Verification when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Spring Boot Verification Loop
Run before PRs, after major changes, and pre-deploy.
## When to Activate
- Before opening a pull request for a Spring Boot service - After major refactoring or dependency upgrades - Pre-deployment verification for staging or production - Running full build → lint → test → security scan pipeline - Validating test coverage meets thresholds
## Phase 1: Build
```bash mvn -T 4 clean verify -DskipTests # or ./gradlew clean assemble -x test ```
If build fails, stop and fix.
## Phase 2: Static Analysis
Maven (common plugins): ```bash mvn -T 4 spotbugs:check pmd:check checkstyle:check ```
Gradle (if configured): ```bash ./gradlew checkstyleMain pmdMain spotbugsMain ```
## Phase 3: Tests + Coverage
```bash mvn -T 4 test mvn jacoco:report # verify 80%+ coverage # or ./gradlew test jacocoTestReport ```
Report: - Total tests, passed/failed - Coverage % (lines/branches)
### Unit Tests
Test service logic in isolation with mocked dependencies:
```java @ExtendWith(MockitoExtension.class) class UserServiceTest {
@Mock private UserRepository userRepository; @InjectMocks private UserService userService;
@Test void createUser_validInput_returnsUser() { var dto = new CreateUserDto("Alice", "[email protected]"); var expected = new User(1L, "Alice", "[email protected]"); when(userRepository.save(any(User.class))).thenReturn(expected);
var result = userService.create(dto);
assertThat(result.name()).isEqualTo("Alice"); verify(userRepository).save(any(User.class)); }
@Test void createUser_duplicateEmail_throwsException() { var dto = new CreateUserDto("Alice", "[email protected]"); when(userRepository.existsByEmail(dto.email())).thenReturn(true);
assertThatThrownBy(() -> userService.create(dto)) .isInstanceOf(DuplicateEmailException.class); } } ```
### Integration Tests with Testcontainers
Test against a real database instead of H2:
```java @SpringBootTest @Testcontainers class UserRepositoryIntegrationTest {
@Container static PostgreSQLContainer<?> postgres = new PostgreSQLContainer<>("postgres:16-alpine") .withDatabaseName("testdb");
@DynamicPropertySource static void configureProperties(DynamicPropertyRegistry registry) { registry.add("spring.datasource.url", postgres::getJdbcUrl); registry.add("spring.datasource.username", postgres::getUsername); registry.add("spring.datasource.password", postgres::getPassword); }
@Autowired private UserRepository userRepository;
@Test void findByEmail_existingUser_returnsUser() { userRepository.save(new User("Alice", "[email protected]"));
var found = userRepository.findByEmail("[email protected]");
assertThat(found).isPresent(); assertThat(found.get().getName()).isEqualTo("Alice"); } } ```
### API Tests with MockMvc
Test controller layer with full Spring context:
```java @WebMvcTest(UserController.class) class UserControllerTest {
@Autowired private MockMvc mockMvc; @MockBean private UserService userService;
@Test void createUser_validInput_returns201() throws Exception { var user = new UserDto(1L, "Alice", "[email protected]"); when(userService.create(any())).thenReturn(user);
mockMvc.perform(post("/api/users") .contentType(MediaType.APPLICATION_JSON) .content(""" {"name": "Alice", "email": "[email protected]"} """)) .andExpect(status().isCreated()) .andExpect(jsonPath("$.name").value("Alice")); }
@Test void createUser_invalidEmail_returns400() throws Exception { mockMvc.perform(post("/api/users") .contentType(MediaType.APPLICATION_JSON) .content(""" {"name": "Alice", "email": "not-an-email"} """)) .andExpect(status().isBadRequest()); } } ```
## Phase 4: Security Scan
```bash # Dependency CVEs mvn org.owasp:dependency-check-maven:check # or ./gradlew dependencyCheckAnalyze
# Secrets in source grep -rn "password\s*=\s*\"" src/ --include="*.java" --include="*.yml" --include="*.properties" grep -rn "sk-\|api_key\|secret" src/ --include="*.java" --include="*.yml"
# Secrets (git history) git secrets --scan # if configured ```
### Common Security Findings
``` # Check for System.out.println (use logger instead) grep -rn "System\.out\.print" src/main/ --include="*.java"
# Check for raw exception messages in responses grep -rn "e\.getMessage()" src/main/ --include="*.java"
# Check for wildcard CORS grep -rn "allowedOrigins.*\*" src/main/ --include="*.java" ```
## Phase 5: Lint/Format (optional gate)
```bash mvn spotless:apply # if using Spotless plugin ./gradlew spotlessApply ```
## Phase 6: Diff Review
```bash git diff --stat git diff ```
Checklist: - No debugging logs left (`System.out`, `log.debug` without guards) - Meaningful errors and HTTP statuses - Transactions and validation present where needed - Config changes documented
## Output Template
``` VERIFICATION REPORT =================== Build: [PASS/FAIL] Static: [PASS/FAIL] (spotbugs/pmd/checkstyle) Tests: [PASS/FAIL] (X/Y passed, Z% coverage) Security: [PASS/FAIL] (CVE findings: N) Diff: [X files changed]
Overall: [READY / NOT READY]
Issues to Fix: 1. ... 2. ... ```
## Continuous Mode
- Re-run phases on significant changes or every 30–60 minutes in long sessions - Keep a short loop: `mvn -T 4 test` + spotbugs for quick feedback
**Remember**: Fast feedback beats late surprises. Keep the gate strict—treat warnings as defects in production systems.
Intended uses
- Use Springboot Verification when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.