[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD5GN1VJS9TER0M0848JTT":3,"skill-same:01M6AD5GN1VJS9TER0M0848JTT":99},{"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":31,"publishedAt":64,"linkOnly":65,"markdownContent":66,"markdownBody":67,"frontMatter":68,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":72,"repositoryHtmlUrl":73,"repositoryHomepageUrl":74,"ownerHtmlUrl":75,"ownerBlogUrl":76,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M6AD5GN1VJS9TER0M0848JTT","api-breaking-change-detector",null,"Cross-references C# Web API controllers\u002FDTOs against their TypeScript\u002FJavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-written\u002Fauto-generated HTTP clients like Fetch, Axios, NSwag) to catch contract drift in both directions: backend changes that break client applications (renamed\u002Fremoved JSON keys, new required parameters, status code shifts) and frontend code sending fields the backend no longer reads. Works directly against source code, not exported OpenAPI spec files. Use when the user asks to check for breaking API changes, verify frontend\u002Fbackend contract sync, or audit a DTO\u002Fcontroller change against its TypeScript\u002FJS consumers before merging. Not for generating new API code from a spec (see openapi-to-application-code) or scaffolding new endpoints (see aspnet-minimal-api-openapi).","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fapi-breaking-change-detector\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63],"breaking change","api","api breaking change detector","detector","change","svelte","generated","auto","files","drift","scaffolding","new","auto-generated","directions","axios","dto","when","frontend","fetch","angular","vue","audit","code","http","api changes","status","sync","react","web","javascript","typescript","spec","2026-11-10 10:12:30",false,"---\nname: api-breaking-change-detector\ndescription: \"Cross-references C# Web API controllers\u002FDTOs against their TypeScript\u002FJavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-written\u002Fauto-generated HTTP clients like Fetch, Axios, NSwag) to catch contract drift in both directions: backend changes that break client applications (renamed\u002Fremoved JSON keys, new required parameters, status code shifts) and frontend code sending fields the backend no longer reads. Works directly against source code, not exported OpenAPI spec files. Use when the user asks to check for breaking API changes, verify frontend\u002Fbackend contract sync, or audit a DTO\u002Fcontroller change against its TypeScript\u002FJS consumers before merging. Not for generating new API code from a spec (see openapi-to-application-code) or scaffolding new endpoints (see aspnet-minimal-api-openapi).\"\n---\n\n# API Breaking Change Detector\n\nYou are cross-referencing a C# Web API's actual contract (controllers, DTOs, route definitions) against its TypeScript\u002FJavaScript consumers to find contract drift — in both directions — before it reaches production.\n\n## When to use this\n\nTrigger when the user asks to:\n- Check whether a DTO\u002Fcontroller change will break frontend or client applications\n- Verify the client and backend API contract are still in sync\n- Audit a specific endpoint, or the whole API surface, for breaking changes before a release\n\nDo not use this for:\n- Generating new API code from an OpenAPI spec (see `openapi-to-application-code`)\n- Scaffolding new endpoints with OpenAPI docs (see `aspnet-minimal-api-openapi`)\n- Comparing two OpenAPI spec *files* directly — this skill reads source code, not exported specs\n\n## Process\n\n1. **Discover Global JSON & Naming Policies:**\n   - Check `Program.cs` or `Startup.cs` for active JSON options (e.g. `JsonNamingPolicy.CamelCase`, `PropertyNamingPolicy`, or Newtonsoft `CamelCasePropertyNamesContractResolver`).\n   - Default to `camelCase` for TypeScript\u002FJavaScript field mapping if global camelCase is configured, unless overridden by an explicit `[JsonPropertyName(\"...\")]` attribute on the C# property.\n   - Ignore C# properties annotated with `[JsonIgnore]`.\n\n2. **Identify the C# contract surface.** For each Controller action in scope:\n   - **Route**: Base `[Route(\"...\")]` + action `[HttpGet(\"...\")]` \u002F `[HttpPost(\"...\")]`. Normalize route parameters (e.g. `{id:int}` or `{id:guid}` $\\rightarrow$ `{id}`).\n   - **Request DTO**: Extract property names, types, and requirement rules:\n     - *Required if*: annotated with `[Required]`, `[BindRequired]`, has the C# 11 `required` modifier (`public required string X`), or is a non-nullable value type (`int`, `Guid`, `bool`) without a default value.\n     - *Optional if*: nullable (`string?`, `int?`), or has a default initializer.\n   - **Response DTO**: Property names, types, and nullability.\n   - **Explicit Status Codes**: `[ProducesResponseType(statusCode)]` attributes and explicit `StatusCode(...)` return paths.\n\n3. **Find the matching TypeScript\u002FJavaScript consumer (with Normalized URL Matching):**\n   - **Auto-generated client match (high confidence):** look for generated client files (NSwag\u002FOpenAPI Generator output) and match by generated method\u002Finterface name directly.\n   - **Hand-written service\u002Fclient match (medium confidence):** \n     - Search TypeScript\u002FJavaScript files for HTTP client calls (`fetch`, `axios`, Angular `HttpClient`, `ky`, etc.) whose normalized URL pattern matches the controller's route.\n     - Normalize template strings and concatenations (e.g., `${this.apiUrl}\u002Fusers\u002F${id}` or `baseUrl + '\u002Fusers\u002F' + userId` $\\rightarrow$ `\u002Fusers\u002F{id}`).\n     - Match normalized routes against C# routes regardless of variable naming in TypeScript\u002FJS.\n   - **No match found:** report as \"no client consumer located\" rather than guessing — do not assume an endpoint is unused just because a match wasn't found statically.\n   - Label every finding with which of these three methods was used to locate it.\n\n4. **Compare backend → frontend\u002Fclient (breaks the client):**\n   - A DTO property renamed or removed that the TypeScript\u002FJS interface or object model still expects\n   - A new required request field the client never sends\n   - A response status code the client doesn't handle (e.g. controller now returns 409 Conflict, but client error handler only handles 400\u002F500)\n   - A response field's type changed (e.g. `long` $\\rightarrow$ `string`, or non-nullable $\\rightarrow$ nullable) in a way the client type assumes differently\n\n5. **Compare frontend\u002Fclient → backend (stale\u002Fdead client code vs. silent bugs):**\n   - *Harmless dead field*: Client sends a payload property the backend ignores without error.\n   - *Silently broken bug (High Severity)*: Client logic reads a response property that the backend no longer returns (resulting in `undefined` at runtime and potential application failures).\n\n6. **Produce the report** (see Output Format). This skill does not modify code.\n\n## Output Format\n\n1. **Scope Audited** — Controllers, DTOs, and TypeScript\u002FJavaScript files audited, along with detected JSON naming policies (e.g. `camelCase` enabled via `Program.cs`).\n2. **Backend → Client Breaks** — Grouped by endpoint: what changed, match method used (Auto-generated \u002F Normalized Route Match), exact impact on the client, and severity (Compilation Error vs. Silent Runtime Failure).\n3. **Client → Backend Drift** — Stale fields sent or expected, explicitly distinguishing harmless dead fields from silently broken client UI logic.\n4. **No Consumer Found** — Unmatched backend DTOs\u002Fendpoints requiring manual confirmation.\n5. **Match Confidence Summary** — Breakdown of findings derived from auto-generated clients vs. normalized hand-written routes vs. unmatched routes.\n\n## Guidelines\n\n- **URL Normalization**: Always strip query parameters (`?status=active`) and normalize path parameters (`${id}` \u002F `:id` \u002F `{id}`) before comparing routes.\n- **Naming Policies**: Never assume a C# property name matches a TypeScript\u002FJS property verbatim without checking for `[JsonPropertyName(\"...\")]` or global `JsonNamingPolicy.CamelCase` settings.\n- **Modern C# Nuances**: Check for C# 11 `required` keyword and `#nullable enable` annotations (`string?` vs `string`) when assessing required properties.\n- **Framework Agnostic**: Apply contract matching across any TypeScript or JavaScript client (Fetch, Axios, Angular, React, Vue, Svelte, Node.js).\n- **Never Fabricate**: If no matching client service or DTO is found, report \"No consumer located via static search\" — never guess a pairing based purely on loose class names.\n- **Reporting Only**: Do not modify code; output a scannable, actionable audit report.","# API Breaking Change Detector\n\nYou are cross-referencing a C# Web API's actual contract (controllers, DTOs, route definitions) against its TypeScript\u002FJavaScript consumers to find contract drift — in both directions — before it reaches production.\n\n## When to use this\n\nTrigger when the user asks to:\n- Check whether a DTO\u002Fcontroller change will break frontend or client applications\n- Verify the client and backend API contract are still in sync\n- Audit a specific endpoint, or the whole API surface, for breaking changes before a release\n\nDo not use this for:\n- Generating new API code from an OpenAPI spec (see `openapi-to-application-code`)\n- Scaffolding new endpoints with OpenAPI docs (see `aspnet-minimal-api-openapi`)\n- Comparing two OpenAPI spec *files* directly — this skill reads source code, not exported specs\n\n## Process\n\n1. **Discover Global JSON & Naming Policies:**\n   - Check `Program.cs` or `Startup.cs` for active JSON options (e.g. `JsonNamingPolicy.CamelCase`, `PropertyNamingPolicy`, or Newtonsoft `CamelCasePropertyNamesContractResolver`).\n   - Default to `camelCase` for TypeScript\u002FJavaScript field mapping if global camelCase is configured, unless overridden by an explicit `[JsonPropertyName(\"...\")]` attribute on the C# property.\n   - Ignore C# properties annotated with `[JsonIgnore]`.\n\n2. **Identify the C# contract surface.** For each Controller action in scope:\n   - **Route**: Base `[Route(\"...\")]` + action `[HttpGet(\"...\")]` \u002F `[HttpPost(\"...\")]`. Normalize route parameters (e.g. `{id:int}` or `{id:guid}` $\\rightarrow$ `{id}`).\n   - **Request DTO**: Extract property names, types, and requirement rules:\n     - *Required if*: annotated with `[Required]`, `[BindRequired]`, has the C# 11 `required` modifier (`public required string X`), or is a non-nullable value type (`int`, `Guid`, `bool`) without a default value.\n     - *Optional if*: nullable (`string?`, `int?`), or has a default initializer.\n   - **Response DTO**: Property names, types, and nullability.\n   - **Explicit Status Codes**: `[ProducesResponseType(statusCode)]` attributes and explicit `StatusCode(...)` return paths.\n\n3. **Find the matching TypeScript\u002FJavaScript consumer (with Normalized URL Matching):**\n   - **Auto-generated client match (high confidence):** look for generated client files (NSwag\u002FOpenAPI Generator output) and match by generated method\u002Finterface name directly.\n   - **Hand-written service\u002Fclient match (medium confidence):** \n     - Search TypeScript\u002FJavaScript files for HTTP client calls (`fetch`, `axios`, Angular `HttpClient`, `ky`, etc.) whose normalized URL pattern matches the controller's route.\n     - Normalize template strings and concatenations (e.g., `${this.apiUrl}\u002Fusers\u002F${id}` or `baseUrl + '\u002Fusers\u002F' + userId` $\\rightarrow$ `\u002Fusers\u002F{id}`).\n     - Match normalized routes against C# routes regardless of variable naming in TypeScript\u002FJS.\n   - **No match found:** report as \"no client consumer located\" rather than guessing — do not assume an endpoint is unused just because a match wasn't found statically.\n   - Label every finding with which of these three methods was used to locate it.\n\n4. **Compare backend → frontend\u002Fclient (breaks the client):**\n   - A DTO property renamed or removed that the TypeScript\u002FJS interface or object model still expects\n   - A new required request field the client never sends\n   - A response status code the client doesn't handle (e.g. controller now returns 409 Conflict, but client error handler only handles 400\u002F500)\n   - A response field's type changed (e.g. `long` $\\rightarrow$ `string`, or non-nullable $\\rightarrow$ nullable) in a way the client type assumes differently\n\n5. **Compare frontend\u002Fclient → backend (stale\u002Fdead client code vs. silent bugs):**\n   - *Harmless dead field*: Client sends a payload property the backend ignores without error.\n   - *Silently broken bug (High Severity)*: Client logic reads a response property that the backend no longer returns (resulting in `undefined` at runtime and potential application failures).\n\n6. **Produce the report** (see Output Format). This skill does not modify code.\n\n## Output Format\n\n1. **Scope Audited** — Controllers, DTOs, and TypeScript\u002FJavaScript files audited, along with detected JSON naming policies (e.g. `camelCase` enabled via `Program.cs`).\n2. **Backend → Client Breaks** — Grouped by endpoint: what changed, match method used (Auto-generated \u002F Normalized Route Match), exact impact on the client, and severity (Compilation Error vs. Silent Runtime Failure).\n3. **Client → Backend Drift** — Stale fields sent or expected, explicitly distinguishing harmless dead fields from silently broken client UI logic.\n4. **No Consumer Found** — Unmatched backend DTOs\u002Fendpoints requiring manual confirmation.\n5. **Match Confidence Summary** — Breakdown of findings derived from auto-generated clients vs. normalized hand-written routes vs. unmatched routes.\n\n## Guidelines\n\n- **URL Normalization**: Always strip query parameters (`?status=active`) and normalize path parameters (`${id}` \u002F `:id` \u002F `{id}`) before comparing routes.\n- **Naming Policies**: Never assume a C# property name matches a TypeScript\u002FJS property verbatim without checking for `[JsonPropertyName(\"...\")]` or global `JsonNamingPolicy.CamelCase` settings.\n- **Modern C# Nuances**: Check for C# 11 `required` keyword and `#nullable enable` annotations (`string?` vs `string`) when assessing required properties.\n- **Framework Agnostic**: Apply contract matching across any TypeScript or JavaScript client (Fetch, Axios, Angular, React, Vue, Svelte, Node.js).\n- **Never Fabricate**: If no matching client service or DTO is found, report \"No consumer located via static search\" — never guess a pairing based purely on loose class names.\n- **Reporting Only**: Do not modify code; output a scannable, actionable audit report.",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fapi-breaking-change-detector",5344,"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-13 02:05:36",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add github\u002Fawesome-copilot --skill api-breaking-change-detector",{"tool":85,"command":86},"bunx","bunx skills add github\u002Fawesome-copilot --skill api-breaking-change-detector",{"tool":88,"command":89},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill api-breaking-change-detector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fapi-breaking-change-detector\u002FSKILL.md",true,[93],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"agents\u002Fopenai.yaml","REFERENCE","参考文档",257,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-xhs-title\u002Fagents\u002Fopenai.yaml",[100,131,157,182,213,230],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":112,"publishedAt":64},"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",[106,109],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[113,114,115,116,117,48,118,36,119,120,121,122,123,124,125,126,127,128,129,130],"supabase","rls","supabase rls","supabase rls policies","project","review","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":64},"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",[137],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},[139,140,53,141,142,143,144,145,146,147,148,149,150,41,151,152,153,154,155,156],"distribution","skill distribution audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","output","investigate","duplicate","template","release","reconcile",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":64},"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",[164],{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[166,54,167,168,169,170,144,117,171,172,173,174,175,176,177,127,178,179,180,181],"custom","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":64},"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",[189,190],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[192,193,33,194,195,196,197,198,199,200,201,202,203,204,205,48,206,207,208,209,210,144,211,212],"winmd api search","search","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":217,"licenseFileUrl":218,"sourceHtmlUrl":219,"categories":220,"keywords":226,"publishedAt":64},"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",[221,222,225],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},[227,141,200,228,229],"resemble detect","https","identity",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":217,"licenseFileUrl":234,"sourceHtmlUrl":235,"categories":236,"keywords":241,"publishedAt":64},"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",[237,240],{"categoryNo":238,"categoryName":239,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},[242,243,244,245,54,118,9,53,246,247,228,248,63,249,250,251,252,253,254,255,256,257,125,258,259,260,261],"playbook","quality playbook","quality","code review","tdd","run","report","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]