[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADRKHNWDWJR5YDFASAX3CH":3,"skill-same:01M6ADRKHNWDWJR5YDFASAX3CH":89},{"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":18,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6ADRKHNWDWJR5YDFASAX3CH","java-testcontainers",null,"Write reliable integration tests in plain Java with Testcontainers 2.x: JUnit Jupiter lifecycle, singleton containers, reuse, generic containers, wait strategies, networks, init scripts, Docker Compose, CI and Docker\u002FPodman setup. Use when adding or fixing Testcontainers tests, or migrating from 1.x. Framework-neutral.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-testcontainers\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"testcontainers","java","java testcontainers","when","containers","generic","singleton","reuse","tests","jupiter","compose","use","lifecycle","networks","ci","integration","framework","podman","docker compose","setup","init","integration tests","docker","2026-11-10 10:12:30",false,"---\nname: java-testcontainers\ndescription: 'Write reliable integration tests in plain Java with Testcontainers 2.x: JUnit Jupiter lifecycle, singleton containers, reuse, generic containers, wait strategies, networks, init scripts, Docker Compose, CI and Docker\u002FPodman setup. Use when adding or fixing Testcontainers tests, or migrating from 1.x. Framework-neutral.'\n---\n\n# Java Testcontainers (2.x)\n\nRun real dependencies (databases, brokers, caches) in Docker for integration tests. This skill is framework-neutral. If the project uses Spring Boot and the `spring-boot-testing` skill is installed, use it for `@ServiceConnection`, `@DynamicPropertySource` and test slices; for Quarkus, rely on Dev Services (Quarkus skills\u002Fdocs), not hand-wired containers.\n\n## Workflow\n\n1. Detect the existing version (`pom.xml` \u002F `build.gradle`) and test framework (JUnit Jupiter). Testcontainers 2.x has no JUnit 4 support.\n2. Pick the smallest container that matches production (same DB engine and major version; never H2 as a stand-in for behavior you care about).\n3. Choose a lifecycle (table below), configure waiting, wire connection details into the code under test.\n4. Run locally and in CI; check Docker availability and speed.\n\n## Testcontainers 2.x essentials\n\n- Artifacts are all prefixed `testcontainers-`: `org.testcontainers:testcontainers-junit-jupiter`, `testcontainers-postgresql`, `testcontainers-mysql`, `testcontainers-kafka`, etc. (1.x: `junit-jupiter`, `postgresql`). Core stays `org.testcontainers:testcontainers`.\n- Module container classes moved to per-module packages, e.g. `org.testcontainers.postgresql.PostgreSQLContainer` (1.x: `org.testcontainers.containers.PostgreSQLContainer`). Core classes (`GenericContainer`, `Network`, `wait.strategy.*`) remain under `org.testcontainers.containers`.\n- Module container classes are no longer generic: `PostgreSQLContainer`, not `PostgreSQLContainer\u003C?>`.\n- Use a BOM to keep versions aligned: `org.testcontainers:testcontainers-bom:2.0.5` (verify the current release on Maven Central).\n- Docker Compose: use `ComposeContainer` (Compose v2); `DockerComposeContainer` is still present in 2.0.5 (older API); prefer `ComposeContainer`.\n\n```xml\n\u003CdependencyManagement>\n  \u003Cdependencies>\n    \u003Cdependency>\n      \u003CgroupId>org.testcontainers\u003C\u002FgroupId>\n      \u003CartifactId>testcontainers-bom\u003C\u002FartifactId>\n      \u003Cversion>2.0.5\u003C\u002Fversion>\n      \u003Ctype>pom\u003C\u002Ftype>\n      \u003Cscope>import\u003C\u002Fscope>\n    \u003C\u002Fdependency>\n  \u003C\u002Fdependencies>\n\u003C\u002FdependencyManagement>\n\u003Cdependencies>\n  \u003Cdependency>\n    \u003CgroupId>org.testcontainers\u003C\u002FgroupId>\n    \u003CartifactId>testcontainers-junit-jupiter\u003C\u002FartifactId>\n    \u003Cscope>test\u003C\u002Fscope>\n  \u003C\u002Fdependency>\n  \u003Cdependency>\n    \u003CgroupId>org.testcontainers\u003C\u002FgroupId>\n    \u003CartifactId>testcontainers-postgresql\u003C\u002FartifactId>\n    \u003Cscope>test\u003C\u002Fscope>\n  \u003C\u002Fdependency>\n  \u003Cdependency>\n    \u003CgroupId>org.postgresql\u003C\u002FgroupId>\n    \u003CartifactId>postgresql\u003C\u002FartifactId>\n    \u003Cversion>42.7.14\u003C\u002Fversion>\n    \u003Cscope>test\u003C\u002Fscope>\n  \u003C\u002Fdependency>\n\u003C\u002Fdependencies>\n```\n\nGradle: `testImplementation platform(\"org.testcontainers:testcontainers-bom:2.0.5\")`, then the same Testcontainers artifacts without versions, plus `testRuntimeOnly \"org.postgresql:postgresql:42.7.14\"`. The Testcontainers module does not bundle the JDBC driver; skip the explicit driver when the project already depends on one (e.g. via Spring Boot's BOM).\n\n## Minimal test\n\n```java\nimport org.junit.jupiter.api.Test;\nimport org.testcontainers.junit.jupiter.Container;\nimport org.testcontainers.junit.jupiter.Testcontainers;\nimport org.testcontainers.postgresql.PostgreSQLContainer;\n\n@Testcontainers\nclass CustomerStoreIT {\n\n    @Container\n    static final PostgreSQLContainer POSTGRES = new PostgreSQLContainer(\"postgres:17-alpine\");\n\n    @Test\n    void connects() throws Exception {\n        try (var c = java.sql.DriverManager.getConnection(\n                POSTGRES.getJdbcUrl(), POSTGRES.getUsername(), POSTGRES.getPassword())) {\n            org.junit.jupiter.api.Assertions.assertTrue(c.isValid(2));\n        }\n    }\n}\n```\n\nAlways pin the image tag (never `latest`); match the production major version.\n\n## Lifecycle decision\n\n| Need | Pattern |\n| --- | --- |\n| One container per test class | `static @Container` field |\n| Fresh container per test method (slow, strong isolation) | non-static `@Container` field |\n| One container for the whole test run (fastest) | singleton holder, see `references\u002Flifecycle-and-reuse.md` |\n| Keep containers between local runs | `withReuse(true)` + opt-in property, local only |\n\nPrefer sharing a container and isolating **data** (truncate\u002Frollback, unique schema or DB per test) over restarting containers.\n\n## Checklist\n\n- [ ] Image tag pinned and matches production.\n- [ ] Wait strategy meaningful (module defaults are usually fine; custom for `GenericContainer`).\n- [ ] No fixed host ports; use `getMappedPort`\u002F`getHost`.\n- [ ] Containers shared across classes where possible (singleton).\n- [ ] Integration tests named `*IT` and run by failsafe (Maven) or a separate Gradle test task, so unit tests stay fast.\n- [ ] No secrets or real credentials in test containers.\n- [ ] CI runner has Docker; log output is captured on failure.\n\n## References\n\n- `references\u002Flifecycle-and-reuse.md`: per-class\u002Fper-method, singleton pattern, reuse, parallel runs, data isolation.\n- `references\u002Fcontainers-and-waiting.md`: modules vs `GenericContainer`, wait strategies, env\u002Fconfig, init scripts, copy files, networks, multi-container setups, Docker Compose.\n- `references\u002Fenvironment-ci-troubleshooting.md`: Docker\u002FPodman\u002FColima setup, CI, private registries, performance, common errors, 1.x to 2.x migration table.\n\nOfficial docs: \u003Chttps:\u002F\u002Fjava.testcontainers.org\u002F>\n\nUpgrading to 2.x: no dedicated migration page was found on java.testcontainers.org; read the 2.0.0 release notes \u003Chttps:\u002F\u002Fgithub.com\u002Ftestcontainers\u002Ftestcontainers-java\u002Freleases\u002Ftag\u002F2.0.0> and all releases \u003Chttps:\u002F\u002Fgithub.com\u002Ftestcontainers\u002Ftestcontainers-java\u002Freleases> for the target version, and prefer them over this skill when they conflict.\n","# Java Testcontainers (2.x)\n\nRun real dependencies (databases, brokers, caches) in Docker for integration tests. This skill is framework-neutral. If the project uses Spring Boot and the `spring-boot-testing` skill is installed, use it for `@ServiceConnection`, `@DynamicPropertySource` and test slices; for Quarkus, rely on Dev Services (Quarkus skills\u002Fdocs), not hand-wired containers.\n\n## Workflow\n\n1. Detect the existing version (`pom.xml` \u002F `build.gradle`) and test framework (JUnit Jupiter). Testcontainers 2.x has no JUnit 4 support.\n2. Pick the smallest container that matches production (same DB engine and major version; never H2 as a stand-in for behavior you care about).\n3. Choose a lifecycle (table below), configure waiting, wire connection details into the code under test.\n4. Run locally and in CI; check Docker availability and speed.\n\n## Testcontainers 2.x essentials\n\n- Artifacts are all prefixed `testcontainers-`: `org.testcontainers:testcontainers-junit-jupiter`, `testcontainers-postgresql`, `testcontainers-mysql`, `testcontainers-kafka`, etc. (1.x: `junit-jupiter`, `postgresql`). Core stays `org.testcontainers:testcontainers`.\n- Module container classes moved to per-module packages, e.g. `org.testcontainers.postgresql.PostgreSQLContainer` (1.x: `org.testcontainers.containers.PostgreSQLContainer`). Core classes (`GenericContainer`, `Network`, `wait.strategy.*`) remain under `org.testcontainers.containers`.\n- Module container classes are no longer generic: `PostgreSQLContainer`, not `PostgreSQLContainer\u003C?>`.\n- Use a BOM to keep versions aligned: `org.testcontainers:testcontainers-bom:2.0.5` (verify the current release on Maven Central).\n- Docker Compose: use `ComposeContainer` (Compose v2); `DockerComposeContainer` is still present in 2.0.5 (older API); prefer `ComposeContainer`.\n\n```xml\n\u003CdependencyManagement>\n  \u003Cdependencies>\n    \u003Cdependency>\n      \u003CgroupId>org.testcontainers\u003C\u002FgroupId>\n      \u003CartifactId>testcontainers-bom\u003C\u002FartifactId>\n      \u003Cversion>2.0.5\u003C\u002Fversion>\n      \u003Ctype>pom\u003C\u002Ftype>\n      \u003Cscope>import\u003C\u002Fscope>\n    \u003C\u002Fdependency>\n  \u003C\u002Fdependencies>\n\u003C\u002FdependencyManagement>\n\u003Cdependencies>\n  \u003Cdependency>\n    \u003CgroupId>org.testcontainers\u003C\u002FgroupId>\n    \u003CartifactId>testcontainers-junit-jupiter\u003C\u002FartifactId>\n    \u003Cscope>test\u003C\u002Fscope>\n  \u003C\u002Fdependency>\n  \u003Cdependency>\n    \u003CgroupId>org.testcontainers\u003C\u002FgroupId>\n    \u003CartifactId>testcontainers-postgresql\u003C\u002FartifactId>\n    \u003Cscope>test\u003C\u002Fscope>\n  \u003C\u002Fdependency>\n  \u003Cdependency>\n    \u003CgroupId>org.postgresql\u003C\u002FgroupId>\n    \u003CartifactId>postgresql\u003C\u002FartifactId>\n    \u003Cversion>42.7.14\u003C\u002Fversion>\n    \u003Cscope>test\u003C\u002Fscope>\n  \u003C\u002Fdependency>\n\u003C\u002Fdependencies>\n```\n\nGradle: `testImplementation platform(\"org.testcontainers:testcontainers-bom:2.0.5\")`, then the same Testcontainers artifacts without versions, plus `testRuntimeOnly \"org.postgresql:postgresql:42.7.14\"`. The Testcontainers module does not bundle the JDBC driver; skip the explicit driver when the project already depends on one (e.g. via Spring Boot's BOM).\n\n## Minimal test\n\n```java\nimport org.junit.jupiter.api.Test;\nimport org.testcontainers.junit.jupiter.Container;\nimport org.testcontainers.junit.jupiter.Testcontainers;\nimport org.testcontainers.postgresql.PostgreSQLContainer;\n\n@Testcontainers\nclass CustomerStoreIT {\n\n    @Container\n    static final PostgreSQLContainer POSTGRES = new PostgreSQLContainer(\"postgres:17-alpine\");\n\n    @Test\n    void connects() throws Exception {\n        try (var c = java.sql.DriverManager.getConnection(\n                POSTGRES.getJdbcUrl(), POSTGRES.getUsername(), POSTGRES.getPassword())) {\n            org.junit.jupiter.api.Assertions.assertTrue(c.isValid(2));\n        }\n    }\n}\n```\n\nAlways pin the image tag (never `latest`); match the production major version.\n\n## Lifecycle decision\n\n| Need | Pattern |\n| --- | --- |\n| One container per test class | `static @Container` field |\n| Fresh container per test method (slow, strong isolation) | non-static `@Container` field |\n| One container for the whole test run (fastest) | singleton holder, see `references\u002Flifecycle-and-reuse.md` |\n| Keep containers between local runs | `withReuse(true)` + opt-in property, local only |\n\nPrefer sharing a container and isolating **data** (truncate\u002Frollback, unique schema or DB per test) over restarting containers.\n\n## Checklist\n\n- [ ] Image tag pinned and matches production.\n- [ ] Wait strategy meaningful (module defaults are usually fine; custom for `GenericContainer`).\n- [ ] No fixed host ports; use `getMappedPort`\u002F`getHost`.\n- [ ] Containers shared across classes where possible (singleton).\n- [ ] Integration tests named `*IT` and run by failsafe (Maven) or a separate Gradle test task, so unit tests stay fast.\n- [ ] No secrets or real credentials in test containers.\n- [ ] CI runner has Docker; log output is captured on failure.\n\n## References\n\n- `references\u002Flifecycle-and-reuse.md`: per-class\u002Fper-method, singleton pattern, reuse, parallel runs, data isolation.\n- `references\u002Fcontainers-and-waiting.md`: modules vs `GenericContainer`, wait strategies, env\u002Fconfig, init scripts, copy files, networks, multi-container setups, Docker Compose.\n- `references\u002Fenvironment-ci-troubleshooting.md`: Docker\u002FPodman\u002FColima setup, CI, private registries, performance, common errors, 1.x to 2.x migration table.\n\nOfficial docs: \u003Chttps:\u002F\u002Fjava.testcontainers.org\u002F>\n\nUpgrading to 2.x: no dedicated migration page was found on java.testcontainers.org; read the 2.0.0 release notes \u003Chttps:\u002F\u002Fgithub.com\u002Ftestcontainers\u002Ftestcontainers-java\u002Freleases\u002Ftag\u002F2.0.0> and all releases \u003Chttps:\u002F\u002Fgithub.com\u002Ftestcontainers\u002Ftestcontainers-java\u002Freleases> for the target version, and prefer them over this skill when they conflict.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fjava-testcontainers",5335,"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 11:59:04",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add github\u002Fawesome-copilot --skill java-testcontainers",{"tool":63,"command":64},"bunx","bunx skills add github\u002Fawesome-copilot --skill java-testcontainers",{"tool":66,"command":67},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill java-testcontainers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-testcontainers\u002FSKILL.md",true,[71,77,81,85],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"package.json","REFERENCE","参考文档",863,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsandbox-packs\u002Fsandbox-mammoth\u002Fpackage.json",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fcontainers-and-waiting.md",4360,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-testcontainers\u002Freferences\u002Fcontainers-and-waiting.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fenvironment-ci-troubleshooting.md",4849,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-testcontainers\u002Freferences\u002Fenvironment-ci-troubleshooting.md",{"path":86,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Flifecycle-and-reuse.md",2971,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fjava-testcontainers\u002Freferences\u002Flifecycle-and-reuse.md",[90,122,150,180,214,231],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":104,"publishedAt":42},"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",[96,101],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发",[105,106,107,108,109,22,110,111,112,113,114,115,116,117,27,118,30,119,120,121],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","prove","users","functions","with",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":42},"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",[128],{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":162,"publishedAt":42},"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",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[163,164,165,166,167,168,136,109,169,170,171,172,173,174,175,30,176,177,178,179],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":184,"sourceHtmlUrl":185,"categories":186,"keywords":191,"publishedAt":42},"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",[187,190],{"categoryNo":188,"categoryName":189,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},[192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,22,207,208,209,210,211,136,212,213],"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":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":218,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":227,"publishedAt":42},"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",[222,223,226],{"categoryNo":188,"categoryName":189,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":224,"categoryName":225,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},[228,133,201,229,230],"resemble detect","https","identity",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":218,"licenseFileUrl":235,"sourceHtmlUrl":236,"categories":237,"keywords":242,"publishedAt":42},"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",[238,241],{"categoryNo":239,"categoryName":240,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":102,"categoryName":103,"taxonomyType":99,"taxonomyTypeDesc":100},[243,244,245,246,164,110,9,132,247,248,229,249,250,251,252,253,254,255,256,257,258,259,27,260,261,262,263],"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"]