quarkus-verification

Automate builds, tests, static analysis, security scanning, and native compilation for Quarkus projects.

Updated Jun 22, 2026

Search Tags:#testing #security #verification #build #Quarkus

Ready to run

npx skills add https://github.com/hector-manny/bussbot --skill quarkus-verification-hector-manny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quarkus-verification
Source: https://github.com/hector-manny/bussbot/tree/main/.cursor/skills/quarkus-verification
Command: npx skills add https://github.com/hector-manny/bussbot --skill quarkus-verification-hector-manny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires maven, gradle, sonarqube, OWASP ZAP, K6, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the verification process for Quarkus projects, ensuring they meet quality and security standards before release or deployment.

Core Features & Use Cases

Automated Build and Tests: Execute build and test commands to ensure code quality and functionality.
Static Analysis: Run checks for code smells, potential bugs, and security vulnerabilities.
Security Scanning: Perform security scans to detect vulnerabilities in dependencies and application code.
Native Compilation: Compile the application into a native executable for better performance.
Use Case: Before deploying a Quarkus service, use this Skill to run a full verification pipeline that includes building, testing, security scanning, and native compilation.

Quick Start

Run the 'quarkus-verification' skill to execute the full verification process for your Quarkus 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 project verification for builds, tests, and security scanning?▼

Automate Quarkus project verification by running a pipeline that executes builds, tests, static analysis, security scanning, and native compilation to ensure code quality and security compliance before deployment.

Can I run OWASP ZAP security scans and SonarQube static analysis on my Quarkus application?▼

Yes, Quarkus verification integrates OWASP ZAP for security scans and SonarQube for static analysis to detect code smells, potential bugs, and vulnerabilities in dependencies and application code.

What's the best way to verify a Quarkus service before deployment or during pull request reviews?▼

The best way to verify a Quarkus service before deployment or during pull request reviews is running an automated verification process covering builds, tests, static analysis, and native compilation.

Does Quarkus native compilation work with Maven and Gradle build tools for automated verification?▼

Yes, Quarkus native compilation works with Maven and Gradle build tools to compile the application into a native executable for better performance during the automated verification process.

Why should I include native compilation and K6 load testing in my Quarkus verification pipeline?▼

Including native compilation and K6 load testing in your Quarkus verification pipeline ensures better application performance and validates code quality and security compliance before release.

What are the limitations of automating Quarkus builds with SonarQube and OWASP ZAP?▼

Automating Quarkus builds with SonarQube and OWASP ZAP requires proper configuration of Maven or Gradle dependencies to ensure accurate static analysis and security vulnerability detection.