// Use when asked to build, compile, or rebuild specific Quarkus modules. Accepts multiple module names and builds them in parallel via subagents. Examples - build graphql module, compile openapi and rest, rebuild security extensions.
Use when asked to view changes, show a diff, review what changed, compare branches, or see recent commits in a rich browser interface. Supports unstaged changes, staged changes, branch comparisons, commit ranges, and live watch mode with auto-refresh.
Use when you need to find which JAR contains a Java class, resolve import statements, identify classpath conflicts, or discover which dependency provides a class. Accepts fully qualified class names, simple class names, or partial patterns.
Use when you need to view the source code of a Java class from project dependencies, understand a library's API implementation, find method signatures, or explore how a dependency works internally. Accepts fully qualified or simple class names.
Use when asked to do a full build, complete build, rebuild, or build everything in a Quarkus project. Runs the full Quarkus build with optimized flags via a subagent to keep the main conversation responsive.
| name | quarkus-module-build |
| description | Use when asked to build, compile, or rebuild specific Quarkus modules. Accepts multiple module names and builds them in parallel via subagents. Examples - build graphql module, compile openapi and rest, rebuild security extensions. |
Build one or more specific modules in a Quarkus project with parallel execution.
This skill builds specific Quarkus modules (extensions, libraries, etc.) in parallel using subagents. It's optimized for rapid iteration during development when you only need to rebuild changed modules rather than the entire project.
When NOT to use:
quarkus-full-build instead)mvn test directly)mvn directly)Input format: Module names separated by spaces or "and"
/module-build graphql and openapi/module-build securitybuild the graphql rest and mongodb modulesBuild command per module:
cd <module-path> && mvn clean install -DskipTests
Execution: Parallel via subagents (all modules build simultaneously)
Extract module names from user input (available as $ARGUMENTS):
# Split on spaces and "and"
echo "graphql and openapi rest" | tr ' ' '\n' | grep -v "^and$"
# Result: graphql, openapi, rest
Parsing examples:
graphql and openapi → ["graphql", "openapi"]graphql openapi rest → ["graphql", "openapi", "rest"]build security → ["security"]For each module name, search the project structure:
find . -maxdepth 5 -type f -name "pom.xml" -path "*/<module-name>/*" | head -5
Selection priority:
extensions/<module-name>/ - Extension modules<module-name>/ - Top-level modulesintegration-tests/<module-name>/ - Integration test modulesdevtools/<module-name>/ - Developer toolsExample:
# Looking for "graphql"
find . -maxdepth 5 -type f -name "pom.xml" -path "*/graphql/*" | head -5
Might return:
./extensions/graphql/deployment/pom.xml
./extensions/graphql/runtime/pom.xml
./integration-tests/graphql/pom.xml
Choose the best match:
extensions/graphql/ (parent directory)extensions/graphql/runtime/For each module, dispatch a subagent using the Agent tool. Run all subagents in parallel (multiple Agent calls in one response).
Subagent prompt template:
Build the Quarkus module at: <module-path>
Run the following command:
cd <module-path> && mvn clean install -DskipTests
Monitor the Maven output and report:
1. Whether the build succeeded or failed
2. If failed, include the relevant error output
3. Build time
Module: <module-name>
Example with 3 modules:
Dispatching 3 parallel builds:
Agent 1: Build extensions/graphql/
Agent 2: Build extensions/openapi/
Agent 3: Build extensions/rest/
Each subagent will:
You will be notified as each completes - no polling needed.
After all subagents complete, present a summary:
Format:
Module Build Results (3 modules)
✓ graphql - Built successfully in 2m 15s
✓ openapi - Built successfully in 1m 48s
✗ rest - Build failed
Error in rest module:
[ERROR] /path/to/RestService.java:[23,15] cannot find symbol
symbol: class MissingClass
location: package com.example
The RestService is trying to import a class that doesn't exist.
Next steps: Check if the dependency providing MissingClass is declared in the rest module's pom.xml
After all succeed:
After any fail:
Build with dependencies:
mvn install -DskipTests -am -pl :module-name
-am = "also make" dependencies-pl = "project list" specific moduleBuild without clean:
mvn install -DskipTests
Faster for incremental changes.
Build with tests:
mvn clean install
Use when you need verification.
Common Quarkus patterns:
| Module Type | Path Pattern |
|---|---|
| Extension runtime | extensions/<name>/runtime/ |
| Extension deployment | extensions/<name>/deployment/ |
| Extension parent | extensions/<name>/ |
| Integration test | integration-tests/<name>/ |
| Dev tool | devtools/<name>/ |
| Core | core/<name>/ |
Listing all modules:
find . -name "pom.xml" -path "*/extensions/*" | sed 's|/pom.xml||' | sort
Module not found:
# List all available modules
mvn help:evaluate -Dexpression=project.modules -q -DforceStdout
Build order issues: Build the parent module to resolve dependencies:
cd extensions/<module-name>
mvn clean install -DskipTests
Stale artifacts:
cd <module-path>
mvn clean
mvn install -DskipTests
This skill is platform-agnostic:
The Maven commands are universal across platforms.