Quarkus Dev Services and Testing

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: An existing Quarkus project, local Java tools, and Docker or Podman: Dev Services needs a container runtime to start its PostgreSQL, Kafka, Redis, Keycloak and other containers, and it pulls their images from container registries at use time. No account, no API key and no paid service is needed to install or use the skill itself. Reusing containers across restarts also reads a testcontainers.reuse.enable setting in ~/.testcontainers.properties, as documented in SKILL.md. Nothing is sent anywhere by the skill itself: tests and Dev Services run locally against local containers. Install "Quarkus Dev Services and Testing" for me. Quarkus Dev Services and testing for an existing Quarkus project. In dev and test modes Dev Services starts containers (PostgreSQL, MySQL, Kafka, Redis, Keycloak and others) automatically when the matching extension is present and no connection is configured. The skill covers the properties that control that (image name, reuse, fixed port, sharing), the test stack (@QuarkusTest, @QuarkusIntegrationTest, RestAssured, InjectMock, TestSecurity, TestProfile, TestTransaction), test resources with QuarkusTestResourceLifecycleManager, and the running rules that cost time when missed: integration tests run in the verify phase through Failsafe, the templates set skipITs to true, and continuous testing runs from dev mode. A single SKILL.md file, with no companion references. Repository: https://github.com/github/awesome-copilot (the skill is the whole skills/quarkus-dev-services-and-testing/ folder at the pinned commit: SKILL.md) Pinned version: install the code at commit cb64ad12e32737ae764becd6885462e9b4c7cb00 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/github/awesome-copilot into a temporary folder, check out commit cb64ad12e32737ae764becd6885462e9b4c7cb00, and copy the skills/quarkus-dev-services-and-testing/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 a7ba8792ac02ac3e2bd7779bc162b9aaa1cdf67b3b56958e847260018f12d5a9 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds one file only: SKILL.md. There is no executable code, no script and no companion reference file. - Nothing is sent anywhere during installation itself; the only download is the skill file from GitHub at the pinned commit. - At use time everything runs locally: Dev Services starts local Docker or Podman containers (their images are pulled from container registries) and tests run against them. No test data is uploaded by the skill. - The reuse option reads ~/.testcontainers.properties for testcontainers.reuse.enable=true, exactly as SKILL.md documents; no other personal file is named. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "quarkus-dev-services-and-testing", keeping every file (SKILL.md). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: sign in or create an account, provide any API key, or install any local tool named in the prerequisites; using the skill is a separate step that only starts when I ask for it, and every paid or authenticated use disclosed above happens only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.