Spring Boot Verification Loop
Verify a Spring Boot service before every PR with Muse: build, static analysis, tests with JaCoCo coverage, OWASP dependency and secret scans, diff review, and a pass/fail readiness report.
- What
- Verify a Spring Boot service before every PR with Muse: build, static analysis, tests with JaCoCo coverage, OWASP dependency and secret scans, diff review, and a pass/fail readiness report.
- Cost
- Free
- Needs
- Use "Spring Boot Verification Loop" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a pre-PR verification loop for Spring Boot that makes Muse produce a pass or fail readiness report instead of vibes. Six phases, Maven and Gradle variants. Build runs with parallel threads, stopping on the first failure. Static analysis chains SpotBugs, PMD, and Checkstyle. Tests are concrete: Mockito unit tests for service logic including a duplicate-email exception case, Testcontainers integration tests against real Postgres wired with DynamicPropertySource instead of H2, and MockMvc API tests checking 201 and 400 responses, with JaCoCo reporting lines and branches covered. Security scanning runs OWASP dependency-check for CVEs plus greps for secrets in source and yml, System.out.println, raw exception messages in responses, and wildcard CORS origins. An optional Spotless phase handles formatting, and the diff review checklist catches leftover debug logs, weak HTTP statuses, missing transactions, and undocumented config changes. The output is a structured VERIFICATION REPORT template with Build, Static, Tests, Security, Diff lines and an overall READY or NOT READY verdict with issues to fix. A continuous mode is documented for long sessions: re-run the fast loop of mvn test plus SpotBugs every 30 to 60 minutes. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the secret greps are heuristics, real secret management needs dedicated tooling; the gate is only as strict as you keep it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Spring Boot Verification Loop" with your Muse. Prerequisites: none to install. Pure guidance; a Spring Boot Maven or Gradle project helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/springboot-verification/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Run the verification loop on my Spring Boot service before I open the PR: [describe the project]." 3. Work through the phases, fixing issues as they come. Ask Muse for the final VERIFICATION REPORT with the READY/NOT READY verdict. Tip: in long sessions, ask Muse to re-run the fast loop (tests plus SpotBugs) every 30 to 60 minutes. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.