[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE38V2NH8K9TNE2QEW32XZ":3,"skill-same:01M6AE38V2NH8K9TNE2QEW32XZ":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AE38V2NH8K9TNE2QEW32XZ","quarkus-dev-services-and-testing",null,"Quarkus Dev Services and testing: zero-config containers, @QuarkusTest, @QuarkusIntegrationTest, test resources, RestAssured, @InjectMock, profiles and continuous testing. Use when writing or fixing tests in a Quarkus project.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquarkus-dev-services-and-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"testing","dev","services","quarkus dev services and testing","quarkus","writing","containers","test","config","ZeRO","use","project","tests","resources","profiles","when","2026-11-10 10:12:30",false,"---\nname: quarkus-dev-services-and-testing\ndescription: 'Quarkus Dev Services and testing: zero-config containers, @QuarkusTest, @QuarkusIntegrationTest, test resources, RestAssured, @InjectMock, profiles and continuous testing. Use when writing or fixing tests in a Quarkus project.'\n---\n\n# Quarkus Dev Services and Testing\n\nCheck the project's Quarkus version first. Framework-neutral Testcontainers usage can use the optional `java-testcontainers` skill if installed (otherwise see \u003Chttps:\u002F\u002Fjava.testcontainers.org\u002F>); this skill covers only Quarkus-specific features.\n\n## Dev Services\n\nIn dev and test modes Quarkus starts containers (PostgreSQL, MySQL, Kafka, Redis, Keycloak, ...) automatically when the related extension is present and no connection is configured (Docker or Podman required).\n\n```properties\n# Global switch\nquarkus.devservices.enabled=true\n%dev.quarkus.datasource.devservices.image-name=postgres:17\n# Reuse container across restarts (also requires testcontainers.reuse.enable=true in ~\u002F.testcontainers.properties)\nquarkus.datasource.devservices.reuse=true\n# Fixed port (optional)\nquarkus.datasource.devservices.port=5432\n# Share between apps in dev mode\nquarkus.kafka.devservices.shared=true\n```\n\nDisable one with `quarkus.\u003Cext>.devservices.enabled=false`; configuring a URL\u002Fhost explicitly also disables it. Dev UI (`\u002Fq\u002Fdev-ui`) lists running services.\n\n## Tests\n\n```java\n@QuarkusTest\nclass GreetingResourceTest {\n    @Test\n    void hello() {\n        given().when().get(\"\u002Fhello\").then().statusCode(200).body(is(\"Hello\"));\n    }\n}\n```\n\nDependencies, test scope: `io.quarkus:quarkus-junit` (3.31+, what the 3.40 template generates) or `quarkus-junit5` (3.27 template; still published and resolvable on 3.40) and `io.rest-assured:rest-assured`. Keep whichever the project already uses.\n\n- Inject beans in tests with `@Inject`; mock CDI beans with `io.quarkus.test.InjectMock` (`quarkus-junit-mockito`, formerly `quarkus-junit5-mockito`; verified mocking a `PanacheRepository` bean on 3.40.1).\n- Security: `@TestSecurity(user=\"alice\", roles=\"admin\")` (`quarkus-test-security`).\n- Profiles: `@TestProfile(MyProfile.class)` with `QuarkusTestProfile#getConfigOverrides()`; restarts the app, so use sparingly.\n- Transactions: `@TestTransaction` rolls back after the test.\n- `@QuarkusIntegrationTest` runs against the packaged artifact (jar, native binary or container); you cannot inject beans there, only call it over HTTP.\n\n## Test resources\n\n```java\npublic class WireMockResource implements QuarkusTestResourceLifecycleManager {\n    public Map\u003CString,String> start() { \u002F* start, return config overrides *\u002F return Map.of(); }\n    public void stop() { }\n}\n\n@QuarkusTest\n@WithTestResource(WireMockResource.class)   \u002F\u002F io.quarkus.test.common.WithTestResource\nclass MyTest { }\n```\n\n`@WithTestResource` (verified on 3.40.1) applies to the annotated test class; Quarkus restarts the app when the set of resources changes. The older `@QuarkusTestResource` still compiles and runs on 3.40.1 but applies globally to all tests unless `restrictToAnnotatedClass = true`. Do not put `@ConfigProperty` injection points for resource-supplied values in a test class: test classes are scanned as beans, and the app fails to start for other test classes that lack the resource. Prefer Dev Services over custom resources when an extension supports it.\n\n## Running\n\n```bash\n.\u002Fmvnw test                 # unit\u002F@QuarkusTest\n.\u002Fmvnw verify -DskipITs=false  # also runs *IT via maven-failsafe-plugin\n```\n\nGotcha: `*IT` classes (`@QuarkusIntegrationTest`) are run by Failsafe in the `verify` phase, and need the `quarkus-maven-plugin` `build` goal and the failsafe config (with `java.util.logging.manager` and `maven.home` system properties) generated by the project template. `.\u002Fmvnw test` silently skips them, and the 3.27 and 3.40 templates also set `\u003CskipITs>true\u003C\u002FskipITs>`, so plain `.\u002Fmvnw verify` skips them too (verified): pass `-DskipITs=false` (or `-Dnative`, whose profile flips it). With `-Dnative` and a container build on macOS or Windows, the binary is a Linux ELF and the IT fails with `Exit code is: '126'`; use a local Mandrel\u002FGraalVM build for those.\n\nContinuous testing: run `.\u002Fmvnw quarkus:dev` and press `r` to start or re-run tests and `p` to pause them (`h` lists the hotkeys); once running, tests re-run on code changes (`quarkus.test.continuous-testing=enabled|paused|disabled`).\n\nVerified on Quarkus 3.40.1 (JDK 26, Docker Desktop): `@QuarkusTest` with Dev Services PostgreSQL (`postgres:18` by default), `@TestTransaction`, `@TestProfile`, `@TestSecurity`, `@InjectMock`, `*IT` via Failsafe. `@QuarkusTest` and Dev Services on 3.27.6 as well.\n\n## Checklist\n\n- Use Dev Services before writing a custom resource.\n- Keep `@QuarkusTest` classes sharing the same profile\u002Fresources to avoid restarts.\n- Do not hard-code ports; RestAssured uses `quarkus.http.test-port` automatically.\n\nSee also: \u003Chttps:\u002F\u002Fquarkus.io\u002Fguides\u002Fdev-services>, \u003Chttps:\u002F\u002Fquarkus.io\u002Fguides\u002Fgetting-started-testing>; for upgrades use `quarkus update` (\u003Chttps:\u002F\u002Fquarkus.io\u002Fguides\u002Fupdate-quarkus>).\n","# Quarkus Dev Services and Testing\n\nCheck the project's Quarkus version first. Framework-neutral Testcontainers usage can use the optional `java-testcontainers` skill if installed (otherwise see \u003Chttps:\u002F\u002Fjava.testcontainers.org\u002F>); this skill covers only Quarkus-specific features.\n\n## Dev Services\n\nIn dev and test modes Quarkus starts containers (PostgreSQL, MySQL, Kafka, Redis, Keycloak, ...) automatically when the related extension is present and no connection is configured (Docker or Podman required).\n\n```properties\n# Global switch\nquarkus.devservices.enabled=true\n%dev.quarkus.datasource.devservices.image-name=postgres:17\n# Reuse container across restarts (also requires testcontainers.reuse.enable=true in ~\u002F.testcontainers.properties)\nquarkus.datasource.devservices.reuse=true\n# Fixed port (optional)\nquarkus.datasource.devservices.port=5432\n# Share between apps in dev mode\nquarkus.kafka.devservices.shared=true\n```\n\nDisable one with `quarkus.\u003Cext>.devservices.enabled=false`; configuring a URL\u002Fhost explicitly also disables it. Dev UI (`\u002Fq\u002Fdev-ui`) lists running services.\n\n## Tests\n\n```java\n@QuarkusTest\nclass GreetingResourceTest {\n    @Test\n    void hello() {\n        given().when().get(\"\u002Fhello\").then().statusCode(200).body(is(\"Hello\"));\n    }\n}\n```\n\nDependencies, test scope: `io.quarkus:quarkus-junit` (3.31+, what the 3.40 template generates) or `quarkus-junit5` (3.27 template; still published and resolvable on 3.40) and `io.rest-assured:rest-assured`. Keep whichever the project already uses.\n\n- Inject beans in tests with `@Inject`; mock CDI beans with `io.quarkus.test.InjectMock` (`quarkus-junit-mockito`, formerly `quarkus-junit5-mockito`; verified mocking a `PanacheRepository` bean on 3.40.1).\n- Security: `@TestSecurity(user=\"alice\", roles=\"admin\")` (`quarkus-test-security`).\n- Profiles: `@TestProfile(MyProfile.class)` with `QuarkusTestProfile#getConfigOverrides()`; restarts the app, so use sparingly.\n- Transactions: `@TestTransaction` rolls back after the test.\n- `@QuarkusIntegrationTest` runs against the packaged artifact (jar, native binary or container); you cannot inject beans there, only call it over HTTP.\n\n## Test resources\n\n```java\npublic class WireMockResource implements QuarkusTestResourceLifecycleManager {\n    public Map\u003CString,String> start() { \u002F* start, return config overrides *\u002F return Map.of(); }\n    public void stop() { }\n}\n\n@QuarkusTest\n@WithTestResource(WireMockResource.class)   \u002F\u002F io.quarkus.test.common.WithTestResource\nclass MyTest { }\n```\n\n`@WithTestResource` (verified on 3.40.1) applies to the annotated test class; Quarkus restarts the app when the set of resources changes. The older `@QuarkusTestResource` still compiles and runs on 3.40.1 but applies globally to all tests unless `restrictToAnnotatedClass = true`. Do not put `@ConfigProperty` injection points for resource-supplied values in a test class: test classes are scanned as beans, and the app fails to start for other test classes that lack the resource. Prefer Dev Services over custom resources when an extension supports it.\n\n## Running\n\n```bash\n.\u002Fmvnw test                 # unit\u002F@QuarkusTest\n.\u002Fmvnw verify -DskipITs=false  # also runs *IT via maven-failsafe-plugin\n```\n\nGotcha: `*IT` classes (`@QuarkusIntegrationTest`) are run by Failsafe in the `verify` phase, and need the `quarkus-maven-plugin` `build` goal and the failsafe config (with `java.util.logging.manager` and `maven.home` system properties) generated by the project template. `.\u002Fmvnw test` silently skips them, and the 3.27 and 3.40 templates also set `\u003CskipITs>true\u003C\u002FskipITs>`, so plain `.\u002Fmvnw verify` skips them too (verified): pass `-DskipITs=false` (or `-Dnative`, whose profile flips it). With `-Dnative` and a container build on macOS or Windows, the binary is a Linux ELF and the IT fails with `Exit code is: '126'`; use a local Mandrel\u002FGraalVM build for those.\n\nContinuous testing: run `.\u002Fmvnw quarkus:dev` and press `r` to start or re-run tests and `p` to pause them (`h` lists the hotkeys); once running, tests re-run on code changes (`quarkus.test.continuous-testing=enabled|paused|disabled`).\n\nVerified on Quarkus 3.40.1 (JDK 26, Docker Desktop): `@QuarkusTest` with Dev Services PostgreSQL (`postgres:18` by default), `@TestTransaction`, `@TestProfile`, `@TestSecurity`, `@InjectMock`, `*IT` via Failsafe. `@QuarkusTest` and Dev Services on 3.27.6 as well.\n\n## Checklist\n\n- Use Dev Services before writing a custom resource.\n- Keep `@QuarkusTest` classes sharing the same profile\u002Fresources to avoid restarts.\n- Do not hard-code ports; RestAssured uses `quarkus.http.test-port` automatically.\n\nSee also: \u003Chttps:\u002F\u002Fquarkus.io\u002Fguides\u002Fdev-services>, \u003Chttps:\u002F\u002Fquarkus.io\u002Fguides\u002Fgetting-started-testing>; for upgrades use `quarkus update` (\u003Chttps:\u002F\u002Fquarkus.io\u002Fguides\u002Fupdate-quarkus>).\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fquarkus-dev-services-and-testing",5340,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 13:41:32",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add github\u002Fawesome-copilot --skill quarkus-dev-services-and-testing",{"tool":61,"command":62},"bunx","bunx skills add github\u002Fawesome-copilot --skill quarkus-dev-services-and-testing",{"tool":64,"command":65},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill quarkus-dev-services-and-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquarkus-dev-services-and-testing\u002FSKILL.md",true,[],[70,97,125,155,189,206],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":80,"publishedAt":40},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[76,77],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,84,35,39,85,86,87,88,89,90,91,92,36,93,34,94,95,96],"supabase","rls","supabase rls","supabase rls policies","review","change","read","write","security","isolation","tables","as","prove","users","functions","with",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":40},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[103],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":137,"publishedAt":40},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[138,139,140,141,142,143,111,35,144,145,146,147,148,149,150,34,151,152,153,154],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":166,"publishedAt":40},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[162,165],{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},[167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,39,182,183,184,185,186,111,187,188],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":202,"publishedAt":40},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[197,198,201],{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[203,108,176,204,205],"resemble detect","https","identity",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":217,"publishedAt":40},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[213,216],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},[218,219,220,221,139,85,9,107,222,223,204,224,225,226,227,228,229,230,231,232,233,234,36,235,236,237,238],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]