springboot-verification_skill

This skill streamlines Spring Boot verification by automating build, static analysis, tests with coverage, security scans, and diff reviews before release.

JavaScript

46.5k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill affaan-m/everything-claude-code --skill springboot-verification

SKILL.md5.7 KB

Overview

This skill runs a verification loop for Spring Boot services that combines build, static analysis, tests with coverage, security scans, and a diff review before a PR or release. It produces a concise verification report showing pass/fail status for each phase and items to fix so teams can gate changes reliably. The workflow supports Maven and Gradle projects and includes quick continuous-mode checks for fast feedback.

How this skill works

The skill executes a phased pipeline: build (skip tests optional), static analysis (SpotBugs/PMD/Checkstyle), unit/integration/API tests with JaCoCo coverage, dependency and secret scans, optional formatter/linter gates, and a final git diff review. Each phase returns structured results (pass/fail, test counts, coverage %, CVE findings, changed files) and the skill emits a VERIFICATION REPORT template with an overall READY/NOT READY decision. It can run full checks on demand or short loops (tests + spotbugs) for continuous feedback.

When to use it

Before opening a pull request for any Spring Boot service
After major refactors, dependency upgrades, or config changes
Pre-deployment verification for staging or production
To validate that test coverage meets the project threshold
As a recurring continuous check during long development sessions

Best practices

Fail fast on build or test failures and fix immediately
Enforce a coverage threshold (e.g., 80%) and surface gaps in the report
Treat static-analysis warnings as defects for production systems
Run dependency CVE and secret scans (including git history) before release
Use short verification loops for rapid feedback and full runs before PRs

Example use cases

Run full verification before merging a feature branch into main
Validate a dependency upgrade by catching new CVEs or test regressions
Verify integration tests with Testcontainers against a real DB
CI job that emits a VERIFICATION REPORT for PR checks
Local pre-commit hook that runs quick tests + spotbugs and a diff review

FAQ

Yes. The skill runs equivalent commands for Maven and Gradle, including build, static analysis, tests, JaCoCo reports, and dependency checks.

How is test coverage enforced?

The verification includes a JaCoCo report and compares coverage against a configured threshold (commonly 80%); failures are reported in the VERIFICATION REPORT.