quarkus-verification

Automate Quarkus build, static analysis, test coverage, security scanning, and native compilation.

Updated Jan 30, 2026

Search Tags:#testing #security #java #quarkus #ci-cd #native-image

Ready to run

npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill quarkus-verification-thejanajayalath

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quarkus-verification
Source: https://github.com/ThejanaJayalath/Niolla-PM-system/tree/main/.cursor/skills/quarkus-verification
Command: npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill quarkus-verification-thejanajayalath

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires maven, gradle, jacoco, owasp-dependency-check, trivy.

What problem does it solve?

This Skill addresses the complexity of maintaining high-quality Quarkus services by automating the repetitive verification steps required before releases or pull requests.

Core Features & Use Cases

Full Pipeline Automation: Executes build, static analysis, test coverage, and security scanning in a single workflow.
Native Image Validation: Ensures GraalVM native compilation compatibility and performance health.
Use Case: Before merging a feature branch, use this Skill to verify that your code meets 80% test coverage, passes all security vulnerability checks, and successfully builds as a native executable.

Quick Start

Run the quarkus-verification skill to execute the full build, test, and security analysis pipeline on the current project.

Frequently Asked Questions about quarkus-verification

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

FAQPage Schema

How do I automate Quarkus build, test, and security checks in a single workflow?▼

Automate the Quarkus verification lifecycle by running a single pipeline that executes build, static analysis, test coverage, and security scanning. This ensures consistent quality gates before merging branches or preparing releases without manual intervention.

What is GraalVM native image validation for Quarkus applications?▼

GraalVM native image validation ensures your Quarkus application successfully compiles into a native executable and maintains performance health. It verifies compatibility with native compilation requirements as part of the automated verification pipeline.

Does the Quarkus verification pipeline support Maven and Gradle projects?▼

The Quarkus verification pipeline supports both Maven and Gradle projects. It integrates with your existing build system to execute test coverage analysis via JaCoCo and security scanning without requiring build tool migrations.

How do I enforce test coverage and vulnerability checks for Quarkus CI/CD pipelines?▼

Enforce test coverage and vulnerability checks by integrating the Quarkus verification pipeline into your CI/CD workflow. It uses JaCoCo for coverage metrics and OWASP dependency-check plus Trivy to scan for security vulnerabilities before deployment.

Can I use Trivy and OWASP dependency-check for Quarkus security scanning?▼

You can use Trivy and OWASP dependency-check for Quarkus security scanning. The verification pipeline combines both tools to detect vulnerabilities in dependencies and container images as part of the automated deployment readiness checks.

What are the limitations of native image compilation in Quarkus verification workflows?▼

Native image compilation in Quarkus verification workflows requires GraalVM compatibility, which may limit certain dynamic Java features. The pipeline validates this compatibility but cannot resolve unsupported reflection or runtime proxy generation issues automatically.