Guide · Agent skill
How to use the Quarkus Verification Loop agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The quarkus-verification skill gives an AI agent a structured checklist to run before a Quarkus Java service is opened as a pull request or deployed. It is written for Java developers who maintain a Quarkus service and want the same verification steps every time. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and which requirements and safety points to check first.
Quarkus Verification Loopaffaan-m/ECC · MIT Download the skill Quick start
- 1Download the ZIP. Get the quarkus-verification ZIP from this page. It contains SKILL.md.
- 2Unzip the skill. Place the folder in ~/.claude/skills/ for all projects, or in the project's .claude/skills/ for one repository.
- 3Check requirements. Confirm Java, Maven or Gradle, and a Quarkus project are available. Add Docker, SonarQube, GraalVM or other tools only if you plan to use those phases.
- 4Ask for the check. Request the verification in plain language, for example before opening a pull request or deploying to staging.
- 5Review the results. Read the build, test and coverage output, and the JaCoCo report at target/site/jacoco/index.html.
- 6Fix and rerun. Address any failures the agent reports, then ask for the loop again until the checklist passes.
- 7Get human sign-off. Have a person review security findings and approve any production deployment.
What the skill makes the agent do
When installed, the agent follows a 10-phase verification loop on a Quarkus project. The phases cover: build (Maven or Gradle), static analysis (Checkstyle, PMD, SpotBugs, and optionally SonarQube), tests with coverage checks against an 80% line target and a 70% branch target, dependency and API security scans, a GraalVM native build with health-endpoint smoke tests, a load test with k6, health checks, a container image build with trivy and grype scans, configuration validation, and a documentation review.
The skill is written in Spanish and includes the commands and example unit, integration and API test code to use. It says to stop if the build fails and fix compilation errors before continuing.
Install the quarkus-verification skill
Download the ZIP for this skill from this page. It contains one file, SKILL.md. Unzip it so the skill folder sits in one of these locations:
Personal skills apply to all your projects: ~/.claude/skills/. Project skills apply only to one repository: .claude/skills/ inside the project folder.
You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.
- Personal: unzip into ~/.claude/skills/
- Single project: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload
How to trigger the skill with natural requests
You do not need a special command. Ask for the check in ordinary words that match the skill's use cases, such as before a pull request, after a large refactor or dependency update, or before a staging or production deployment. The skill is meant to run the full pipeline (build, lint, test, security scan, native build) when asked for that.
- Run the quarkus verification checklist before I open this PR.
- We upgraded dependencies; check the Quarkus service before deploying to staging.
- Check that test coverage meets the 80% threshold.
- Run the native image checks for this Quarkus service.
Example of what the agent runs
For a Maven project, the first phase runs a build that skips tests. Later phases run static analysis and tests with coverage. The source gives these commands as examples; your project may need different settings.
mvn clean verify -DskipTests
mvn checkstyle:check pmd:check spotbugs:check
mvn clean test
mvn jacoco:report
mvn jacoco:checkRequirements and optional tools
You need Java and Maven or Gradle, plus a Quarkus project. Some phases need more tools. The SonarQube step needs a SonarQube server and a SONAR_TOKEN environment variable. Docker is needed for OWASP ZAP and container builds. trivy, grype, k6 and curl are optional. GraalVM is needed only for native builds. Skip the phases whose tools you do not have.
- Required: Java, Maven or Gradle, a Quarkus project
- Optional: SonarQube server and SONAR_TOKEN
- Optional: Docker (OWASP ZAP and container builds)
- Optional: trivy, grype, k6, curl
- Optional: GraalVM for native builds
Safety notes before you run it
This skill runs scripts and uses the network. Some commands may modify build output or call external services, such as dependency scanners, a SonarQube server, or the k6 and ZAP targets. Check each command before the agent runs it, especially on production-connected machines.
The skill suggests deployment-gating checks but does not replace security sign-off. Keep a human review in the loop for production deployments.
- Review commands before running them against shared or production systems
- Do not put secrets in code; the checklist expects them in environment variables
- Human review is still required before production deployment
What people use it for
- Pre-PR check on a Quarkus REST service before merging
- Verification after upgrading Quarkus or other dependencies
- Pre-deploy gate for a staging release with coverage and health checks
- Native image compatibility check before shipping a GraalVM build
- Generating example unit, integration and API tests for a Quarkus service
Frequently asked questions
How do I install the quarkus verification skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings → Capabilities → Skills.
What do I need to use it?
You need Java, Maven or Gradle, and a Quarkus project. SonarQube, Docker, trivy, grype, k6, curl and GraalVM are optional and only needed for their specific phases.
Is the quarkus verification skill free?
The item is listed under the MIT licence. Check the source repository's licence file for the terms that apply to your use.
Does it work for projects that are not Quarkus?
No. The commands and test patterns are Quarkus- and Maven-specific, so it is not suited to other frameworks. Use it only for Quarkus projects.
Does the skill run commands on my machine?
Yes. The skill runs scripts and uses the network. Some commands may modify build output or call external services, so review them before running, especially against production systems.
Can it replace a security review?
No. The skill suggests deployment-gating checks but does not replace security sign-off. Keep human review for production deployments.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you maintain a Quarkus Java service and want the same pre-PR and pre-deploy checks run every time, with example tests included. Pick something else if your project does not use Quarkus or Maven, or if you need a fully automated production gate with no human review.
Download the skill