メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/quarkusio/quarkusdev-skills --skill quarkus-full-buildコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | quarkus-full-build |
| description | 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. |
Run a complete build of the Quarkus project with optimized settings.
This skill executes a full Quarkus build using Maven with flags optimized for speed and the Quarkus project structure. The build is dispatched to a subagent to keep your main conversation responsive during the long-running compilation.
When NOT to use:
quarkus-module-build instead)mvn compile directly)mvn test directly)Build command:
mvn install -Dquickly -Dno-test-modules -Dskip.gradle.build=true -T 16C -Prelocations
Flags explained:
-Dquickly - Skip tests, formatting checks, and other non-essential tasks-Dno-test-modules - Don't build test-only modules-Dskip.gradle.build=true - Skip Gradle-based builds (Quarkus is Maven)-T 16C - Parallel build with 16 threads per CPU core-Prelocations - Use relocations profile for optimized dependenciesTypical build time: 5-15 minutes (depends on project size and machine)
Use the Agent tool to run the build in a separate context. This keeps the main conversation responsive while the build runs.
Subagent prompt:
Run a full Quarkus build with the following command:
mvn install -Dquickly -Dno-test-modules -Dskip.gradle.build=true -T 16C -Prelocations
Monitor the Maven output and report:
1. Whether the build succeeded or failed
2. If it failed, include the relevant error output (compilation errors, test failures, etc.)
3. Total build time
Do not include the full Maven output unless there are errors.
The subagent will:
You don't need to poll - the subagent will notify when done.
After the subagent completes, summarize:
On success:
✓ Full Quarkus build completed successfully in 8m 42s
The project is ready for testing or deployment.
On failure:
✗ Full Quarkus build failed during compilation
Error in extensions/quarkus-graphql/runtime:
[ERROR] /path/to/GraphQLService.java:[45,23] cannot find symbol
symbol: method getSchema()
location: variable config of type GraphQLConfig
The GraphQLService class is calling a method that doesn't exist in GraphQLConfig.
After success:
After failure:
| Flag | Purpose | When to Use |
|---|---|---|
-Dquickly | Skip tests and checks | Fast feedback during development |
-DskipTests | Skip test execution only | When tests are slow but you want other checks |
-T 1C | Single-threaded | Debugging build order issues |
-T 16C | Parallel (16 threads/core) | Fast builds on powerful machines |
-am | Also make dependencies | Building a module with its dependencies |
-pl module | Build specific module | Testing changes in one module |
Out of memory:
export MAVEN_OPTS="-Xmx4g -XX:MaxMetaspaceSize=1g"
mvn install -Dquickly ...
Stale artifacts:
mvn clean install -Dquickly ...
Dependency resolution issues:
mvn dependency:purge-local-repository
mvn install -Dquickly ...
This skill is platform-agnostic:
The Maven command itself is universal across all platforms.
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.