[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADE7SZYE3Y1CSHMMDE77HD":3,"skill-same:01M6ADE7SZYE3Y1CSHMMDE77HD":109},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6ADE7SZYE3Y1CSHMMDE77HD","csharp-docs",null,"Ensure that C# types are documented with XML comments and follow best practices for documentation.","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\u002Fcsharp-docs\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"docs","csharp","csharp docs","documentation","best practices","xml","types","with","comments","C#","for","2026-11-10 10:12:30",false,"---\nname: csharp-docs\ndescription: 'Ensure that C# types are documented with XML comments and follow best practices for documentation.'\n---\n\n# C# Documentation Best Practices\n\n- Public members should be documented with XML comments.\n- It is encouraged to document internal members as well, especially if they are complex or not self-explanatory.\n\n## Guidance for all APIs\n\n- Use `\u003Csummary>` to provide a brief, one sentence, description of what the type or member does. Start the summary with a present-tense, third-person verb.\n- Use `\u003Cremarks>` for additional information, which can include implementation details, usage notes, or any other relevant context.\n- Use `\u003Csee langword>` for language-specific keywords like `null`, `true`, `false`, `int`, `bool`, etc.\n- Use `\u003Cc>` for inline code snippets.\n- Use `\u003Cexample>` for usage examples on how to use the member.\n  - Use `\u003Ccode>` for code blocks. `\u003Ccode>` tags should be placed within an `\u003Cexample>` tag. Add the language of the code example using the `language` attribute, for example, `\u003Ccode language=\"csharp\">`.\n- Use `\u003Csee cref>` to reference other types or members inline (in a sentence).\n- Use `\u003Cseealso>` for standalone (not in a sentence) references to other types or members in the \"See also\" section of the online docs.\n- Use `\u003Cinheritdoc\u002F>` to inherit documentation from base classes or interfaces.\n  - Unless there is major behavior change, in which case you should document the differences.\n\n## Methods\n\n- Use `\u003Cparam>` to describe method parameters.\n  - The description should be a noun phrase that doesn't specify the data type.\n  - Begin with an introductory article.\n  - If the parameter is a flag enum, start the description with \"A bitwise combination of the enumeration values that specifies...\".\n  - If the parameter is a non-flag enum, start the description with \"One of the enumeration values that specifies...\".\n  - If the parameter is a Boolean, the wording should be of the form \"`\u003Csee langword=\"true\" \u002F>` to ...; otherwise, `\u003Csee langword=\"false\" \u002F>`.\".\n  - If the parameter is an \"out\" parameter, the wording should be of the form \"When this method returns, contains .... This parameter is treated as uninitialized.\".\n- Use `\u003Cparamref>` to reference parameter names in documentation.\n- Use `\u003Ctypeparam>` to describe type parameters in generic types or methods.\n- Use `\u003Ctypeparamref>` to reference type parameters in documentation.\n- Use `\u003Creturns>` to describe what the method returns.\n  - The description should be a noun phrase that doesn't specify the data type.\n  - Begin with an introductory article.\n  - If the return type is Boolean, the wording should be of the form \"`\u003Csee langword=\"true\" \u002F>` if ...; otherwise, `\u003Csee langword=\"false\" \u002F>`.\".\n\n## Constructors\n\n- The summary wording should be \"Initializes a new instance of the \u003CClass> class [or struct].\".\n\n## Properties\n\n- The `\u003Csummary>` should start with:\n  - \"Gets or sets...\" for a read-write property.\n  - \"Gets...\" for a read-only property.\n  - \"Gets [or sets] a value that indicates whether...\" for properties that return a Boolean value.\n- Use `\u003Cvalue>` to describe the value of the property.\n  - The description should be a noun phrase that doesn't specify the data type.\n  - If the property has a default value, add it in a separate sentence, for example, \"The default is `\u003Csee langword=\"false\" \u002F>`\".\n  - If the value type is Boolean, the wording should be of the form \"`\u003Csee langword=\"true\" \u002F>` if ...; otherwise, `\u003Csee langword=\"false\" \u002F>`. The default is ...\".\n\n## Exceptions\n\n- Use `\u003Cexception cref>` to document exceptions thrown by constructors, properties, indexers, methods, operators, and events.\n- Document all exceptions thrown directly by the member.\n- For exceptions thrown by nested members, document only the exceptions users are most likely to encounter.\n- The description of the exception describes the condition under which it's thrown.\n  - Omit \"Thrown if ...\" or \"If ...\" at the beginning of the sentence. Just state the condition directly, for example \"An error occurred when accessing a Message Queuing API.\"\n","# C# Documentation Best Practices\n\n- Public members should be documented with XML comments.\n- It is encouraged to document internal members as well, especially if they are complex or not self-explanatory.\n\n## Guidance for all APIs\n\n- Use `\u003Csummary>` to provide a brief, one sentence, description of what the type or member does. Start the summary with a present-tense, third-person verb.\n- Use `\u003Cremarks>` for additional information, which can include implementation details, usage notes, or any other relevant context.\n- Use `\u003Csee langword>` for language-specific keywords like `null`, `true`, `false`, `int`, `bool`, etc.\n- Use `\u003Cc>` for inline code snippets.\n- Use `\u003Cexample>` for usage examples on how to use the member.\n  - Use `\u003Ccode>` for code blocks. `\u003Ccode>` tags should be placed within an `\u003Cexample>` tag. Add the language of the code example using the `language` attribute, for example, `\u003Ccode language=\"csharp\">`.\n- Use `\u003Csee cref>` to reference other types or members inline (in a sentence).\n- Use `\u003Cseealso>` for standalone (not in a sentence) references to other types or members in the \"See also\" section of the online docs.\n- Use `\u003Cinheritdoc\u002F>` to inherit documentation from base classes or interfaces.\n  - Unless there is major behavior change, in which case you should document the differences.\n\n## Methods\n\n- Use `\u003Cparam>` to describe method parameters.\n  - The description should be a noun phrase that doesn't specify the data type.\n  - Begin with an introductory article.\n  - If the parameter is a flag enum, start the description with \"A bitwise combination of the enumeration values that specifies...\".\n  - If the parameter is a non-flag enum, start the description with \"One of the enumeration values that specifies...\".\n  - If the parameter is a Boolean, the wording should be of the form \"`\u003Csee langword=\"true\" \u002F>` to ...; otherwise, `\u003Csee langword=\"false\" \u002F>`.\".\n  - If the parameter is an \"out\" parameter, the wording should be of the form \"When this method returns, contains .... This parameter is treated as uninitialized.\".\n- Use `\u003Cparamref>` to reference parameter names in documentation.\n- Use `\u003Ctypeparam>` to describe type parameters in generic types or methods.\n- Use `\u003Ctypeparamref>` to reference type parameters in documentation.\n- Use `\u003Creturns>` to describe what the method returns.\n  - The description should be a noun phrase that doesn't specify the data type.\n  - Begin with an introductory article.\n  - If the return type is Boolean, the wording should be of the form \"`\u003Csee langword=\"true\" \u002F>` if ...; otherwise, `\u003Csee langword=\"false\" \u002F>`.\".\n\n## Constructors\n\n- The summary wording should be \"Initializes a new instance of the \u003CClass> class [or struct].\".\n\n## Properties\n\n- The `\u003Csummary>` should start with:\n  - \"Gets or sets...\" for a read-write property.\n  - \"Gets...\" for a read-only property.\n  - \"Gets [or sets] a value that indicates whether...\" for properties that return a Boolean value.\n- Use `\u003Cvalue>` to describe the value of the property.\n  - The description should be a noun phrase that doesn't specify the data type.\n  - If the property has a default value, add it in a separate sentence, for example, \"The default is `\u003Csee langword=\"false\" \u002F>`\".\n  - If the value type is Boolean, the wording should be of the form \"`\u003Csee langword=\"true\" \u002F>` if ...; otherwise, `\u003Csee langword=\"false\" \u002F>`. The default is ...\".\n\n## Exceptions\n\n- Use `\u003Cexception cref>` to document exceptions thrown by constructors, properties, indexers, methods, operators, and events.\n- Document all exceptions thrown directly by the member.\n- For exceptions thrown by nested members, document only the exceptions users are most likely to encounter.\n- The description of the exception describes the condition under which it's thrown.\n  - Omit \"Thrown if ...\" or \"If ...\" at the beginning of the sentence. Just state the condition directly, for example \"An error occurred when accessing a Message Queuing API.\"\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcsharp-docs",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add github\u002Fawesome-copilot --skill csharp-docs",{"tool":51,"command":52},"bunx","bunx skills add github\u002Fawesome-copilot --skill csharp-docs",{"tool":54,"command":55},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill csharp-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcsharp-docs\u002FSKILL.md",true,[59,65,69,73,77,81,85,89,93,97,101,105],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fepistemics.md","REFERENCE","参考文档",6736,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fepistemics.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Finvestigator-prompt.md",5554,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Finvestigator-prompt.md",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fsource-playbook.md",1363,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsource-playbook.md",{"path":74,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fsources\u002Fcode-archaeology.md",1440,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fcode-archaeology.md",{"path":78,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fsources\u002Fdatabricks.md",6994,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fdatabricks.md",{"path":82,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fsources\u002Fdatadog.md",4971,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fdatadog.md",{"path":86,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fsources\u002Fincident-postmortem.md",372,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fincident-postmortem.md",{"path":90,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fsources\u002Flinear.md",2996,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Flinear.md",{"path":94,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fsources\u002Fnotion.md",2853,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fnotion.md",{"path":98,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fsources\u002Fsentry.md",2089,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fsentry.md",{"path":102,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fsources\u002Fslack.md",1336,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsources\u002Fslack.md",{"path":106,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fsynthesizer-prompt.md",7146,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002Freferences\u002Fsynthesizer-prompt.md",[110,144,171,201,235,252],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":124,"publishedAt":30},"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",[116,121],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":122,"categoryName":123,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000023","Skill与智能体开发",[125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,26],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":30},"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",[150],{"categoryNo":122,"categoryName":123,"taxonomyType":119,"taxonomyTypeDesc":120},[152,153,154,155,156,157,29,158,159,160,161,162,163,164,165,166,167,168,169,170],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":183,"publishedAt":30},"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",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[184,185,186,187,188,189,29,129,190,191,192,193,194,195,196,141,197,198,199,200],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":30},"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",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},[213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,130,228,229,230,231,232,29,233,234],"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":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":239,"licenseFileUrl":240,"sourceHtmlUrl":241,"categories":242,"keywords":248,"publishedAt":30},"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",[243,244,247],{"categoryNo":209,"categoryName":210,"taxonomyType":119,"taxonomyTypeDesc":120},{"categoryNo":245,"categoryName":246,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":122,"categoryName":123,"taxonomyType":119,"taxonomyTypeDesc":120},[249,155,222,250,251],"resemble detect","https","identity",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":239,"licenseFileUrl":256,"sourceHtmlUrl":257,"categories":258,"keywords":263,"publishedAt":30},"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",[259,262],{"categoryNo":260,"categoryName":261,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":122,"categoryName":123,"taxonomyType":119,"taxonomyTypeDesc":120},[264,265,266,267,185,131,9,154,268,269,250,270,271,272,273,274,275,276,277,278,279,280,139,281,282,283,284],"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"]