[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADDANSV8MVD3MXHVF7RS0X":3,"skill-same:01M6ADDANSV8MVD3MXHVF7RS0X":60},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6ADDANSV8MVD3MXHVF7RS0X","create-llms",null,"Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https:\u002F\u002Fllmstxt.org\u002F","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41162,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-llms\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"llms","create","create llms","https","file","repository","specification","structure","org","From Scratch","at","scratch","2026-11-10 10:12:30",false,"---\nname: create-llms\ndescription: 'Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https:\u002F\u002Fllmstxt.org\u002F'\n---\n\n# Create LLMs.txt File from Repository Structure\n\nCreate a new `llms.txt` file from scratch in the root of the repository following the official llms.txt specification at https:\u002F\u002Fllmstxt.org\u002F. This file provides high-level guidance to large language models (LLMs) on where to find relevant content for understanding the repository's purpose and specifications.\n\n## Primary Directive\n\nCreate a comprehensive `llms.txt` file that serves as an entry point for LLMs to understand and navigate the repository effectively. The file must comply with the llms.txt specification and be optimized for LLM consumption while remaining human-readable.\n\n## Analysis and Planning Phase\n\nBefore creating the `llms.txt` file, you must complete a thorough analysis:\n\n### Step 1: Review llms.txt Specification\n\n- Review the official specification at https:\u002F\u002Fllmstxt.org\u002F to ensure full compliance\n- Understand the required format structure and guidelines\n- Note the specific markdown structure requirements\n\n### Step 2: Repository Structure Analysis\n\n- Examine the complete repository structure using appropriate tools\n- Identify the primary purpose and scope of the repository\n- Catalog all important directories and their purposes\n- List key files that would be valuable for LLM understanding\n\n### Step 3: Content Discovery\n\n- Identify README files and their locations\n- Find documentation files (`.md` files in `\u002Fdocs\u002F`, `\u002Fspec\u002F`, etc.)\n- Locate specification files and their purposes\n- Discover configuration files and their relevance\n- Find example files and code samples\n- Identify any existing documentation structure\n\n### Step 4: Create Implementation Plan\n\nBased on your analysis, create a structured plan that includes:\n\n- Repository purpose and scope summary\n- Priority-ordered list of essential files for LLM understanding\n- Secondary files that provide additional context\n- Organizational structure for the llms.txt file\n\n## Implementation Requirements\n\n### Format Compliance\n\nThe `llms.txt` file must follow this exact structure per the specification:\n\n1. **H1 Header**: Single line with repository\u002Fproject name (required)\n2. **Blockquote Summary**: Brief description in blockquote format (optional but recommended)\n3. **Additional Details**: Zero or more markdown sections without headings for context\n4. **File List Sections**: Zero or more H2 sections containing markdown lists of links\n\n### Content Requirements\n\n#### Required Elements\n\n- **Project Name**: Clear, descriptive title as H1\n- **Summary**: Concise blockquote explaining the repository's purpose\n- **Key Files**: Essential files organized by category (H2 sections)\n\n#### File Link Format\n\nEach file link must follow: `[descriptive-name](relative-url): optional description`\n\n#### Section Organization\n\nOrganize files into logical H2 sections such as:\n\n- **Documentation**: Core documentation files\n- **Specifications**: Technical specifications and requirements\n- **Examples**: Sample code and usage examples\n- **Configuration**: Setup and configuration files\n- **Optional**: Secondary files (special meaning - can be skipped for shorter context)\n\n### Content Guidelines\n\n#### Language and Style\n\n- Use concise, clear, unambiguous language\n- Avoid jargon without explanation\n- Write for both human and LLM readers\n- Be specific and informative in descriptions\n\n#### File Selection Criteria\n\nInclude files that:\n- Explain the repository's purpose and scope\n- Provide essential technical documentation\n- Show usage examples and patterns\n- Define interfaces and specifications\n- Contain configuration and setup instructions\n\nExclude files that:\n- Are purely implementation details\n- Contain redundant information\n- Are build artifacts or generated content\n- Are not relevant to understanding the project\n\n## Execution Steps\n\n### Step 1: Repository Analysis\n\n1. Examine the repository structure completely\n2. Read the main README.md to understand the project\n3. Identify all documentation directories and files\n4. Catalog specification files and their purposes\n5. Find example files and configuration files\n\n### Step 2: Content Planning\n\n1. Determine the primary purpose statement\n2. Write a concise summary for the blockquote\n3. Group identified files into logical categories\n4. Prioritize files by importance for LLM understanding\n5. Create descriptions for each file link\n\n### Step 3: File Creation\n\n1. Create the `llms.txt` file in the repository root\n2. Follow the exact format specification\n3. Include all required sections\n4. Use proper markdown formatting\n5. Ensure all links are valid relative paths\n\n### Step 4: Validation\n1. Verify compliance with https:\u002F\u002Fllmstxt.org\u002F specification\n2. Check that all links are valid and accessible\n3. Ensure the file serves as an effective LLM navigation tool\n4. Confirm the file is both human and machine readable\n\n## Quality Assurance\n\n### Format Validation\n\n- ✅ H1 header with project name\n- ✅ Blockquote summary (if included)\n- ✅ H2 sections for file lists\n- ✅ Proper markdown link format\n- ✅ No broken or invalid links\n- ✅ Consistent formatting throughout\n\n### Content Validation\n\n- ✅ Clear, unambiguous language\n- ✅ Comprehensive coverage of essential files\n- ✅ Logical organization of content\n- ✅ Appropriate file descriptions\n- ✅ Serves as effective LLM navigation tool\n\n### Specification Compliance\n\n- ✅ Follows https:\u002F\u002Fllmstxt.org\u002F format exactly\n- ✅ Uses required markdown structure\n- ✅ Implements optional sections appropriately\n- ✅ File located at repository root (`\u002Fllms.txt`)\n\n## Example Structure Template\n\n```txt\n# [Repository Name]\n\n> [Concise description of the repository's purpose and scope]\n\n[Optional additional context paragraphs without headings]\n\n## Documentation\n\n- [Main README](README.md): Primary project documentation and getting started guide\n- [Contributing Guide](CONTRIBUTING.md): Guidelines for contributing to the project\n- [Code of Conduct](CODE_OF_CONDUCT.md): Community guidelines and expectations\n\n## Specifications\n\n- [Technical Specification](spec\u002Ftechnical-spec.md): Detailed technical requirements and constraints\n- [API Specification](spec\u002Fapi-spec.md): Interface definitions and data contracts\n\n## Examples\n\n- [Basic Example](examples\u002Fbasic-usage.md): Simple usage demonstration\n- [Advanced Example](examples\u002Fadvanced-usage.md): Complex implementation patterns\n\n## Configuration\n\n- [Setup Guide](docs\u002Fsetup.md): Installation and configuration instructions\n- [Deployment Guide](docs\u002Fdeployment.md): Production deployment guidelines\n\n## Optional\n\n- [Architecture Documentation](docs\u002Farchitecture.md): Detailed system architecture\n- [Design Decisions](docs\u002Fdecisions.md): Historical design decision records\n```\n\n## Success Criteria\n\nThe created `llms.txt` file should:\n1. Enable LLMs to quickly understand the repository's purpose\n2. Provide clear navigation to essential documentation\n3. Follow the official llms.txt specification exactly\n4. Be comprehensive yet concise\n5. Serve both human and machine readers effectively\n6. Include all critical files for project understanding\n7. Use clear, unambiguous language throughout\n8. Organize content logically for easy consumption\n","# Create LLMs.txt File from Repository Structure\n\nCreate a new `llms.txt` file from scratch in the root of the repository following the official llms.txt specification at https:\u002F\u002Fllmstxt.org\u002F. This file provides high-level guidance to large language models (LLMs) on where to find relevant content for understanding the repository's purpose and specifications.\n\n## Primary Directive\n\nCreate a comprehensive `llms.txt` file that serves as an entry point for LLMs to understand and navigate the repository effectively. The file must comply with the llms.txt specification and be optimized for LLM consumption while remaining human-readable.\n\n## Analysis and Planning Phase\n\nBefore creating the `llms.txt` file, you must complete a thorough analysis:\n\n### Step 1: Review llms.txt Specification\n\n- Review the official specification at https:\u002F\u002Fllmstxt.org\u002F to ensure full compliance\n- Understand the required format structure and guidelines\n- Note the specific markdown structure requirements\n\n### Step 2: Repository Structure Analysis\n\n- Examine the complete repository structure using appropriate tools\n- Identify the primary purpose and scope of the repository\n- Catalog all important directories and their purposes\n- List key files that would be valuable for LLM understanding\n\n### Step 3: Content Discovery\n\n- Identify README files and their locations\n- Find documentation files (`.md` files in `\u002Fdocs\u002F`, `\u002Fspec\u002F`, etc.)\n- Locate specification files and their purposes\n- Discover configuration files and their relevance\n- Find example files and code samples\n- Identify any existing documentation structure\n\n### Step 4: Create Implementation Plan\n\nBased on your analysis, create a structured plan that includes:\n\n- Repository purpose and scope summary\n- Priority-ordered list of essential files for LLM understanding\n- Secondary files that provide additional context\n- Organizational structure for the llms.txt file\n\n## Implementation Requirements\n\n### Format Compliance\n\nThe `llms.txt` file must follow this exact structure per the specification:\n\n1. **H1 Header**: Single line with repository\u002Fproject name (required)\n2. **Blockquote Summary**: Brief description in blockquote format (optional but recommended)\n3. **Additional Details**: Zero or more markdown sections without headings for context\n4. **File List Sections**: Zero or more H2 sections containing markdown lists of links\n\n### Content Requirements\n\n#### Required Elements\n\n- **Project Name**: Clear, descriptive title as H1\n- **Summary**: Concise blockquote explaining the repository's purpose\n- **Key Files**: Essential files organized by category (H2 sections)\n\n#### File Link Format\n\nEach file link must follow: `[descriptive-name](relative-url): optional description`\n\n#### Section Organization\n\nOrganize files into logical H2 sections such as:\n\n- **Documentation**: Core documentation files\n- **Specifications**: Technical specifications and requirements\n- **Examples**: Sample code and usage examples\n- **Configuration**: Setup and configuration files\n- **Optional**: Secondary files (special meaning - can be skipped for shorter context)\n\n### Content Guidelines\n\n#### Language and Style\n\n- Use concise, clear, unambiguous language\n- Avoid jargon without explanation\n- Write for both human and LLM readers\n- Be specific and informative in descriptions\n\n#### File Selection Criteria\n\nInclude files that:\n- Explain the repository's purpose and scope\n- Provide essential technical documentation\n- Show usage examples and patterns\n- Define interfaces and specifications\n- Contain configuration and setup instructions\n\nExclude files that:\n- Are purely implementation details\n- Contain redundant information\n- Are build artifacts or generated content\n- Are not relevant to understanding the project\n\n## Execution Steps\n\n### Step 1: Repository Analysis\n\n1. Examine the repository structure completely\n2. Read the main README.md to understand the project\n3. Identify all documentation directories and files\n4. Catalog specification files and their purposes\n5. Find example files and configuration files\n\n### Step 2: Content Planning\n\n1. Determine the primary purpose statement\n2. Write a concise summary for the blockquote\n3. Group identified files into logical categories\n4. Prioritize files by importance for LLM understanding\n5. Create descriptions for each file link\n\n### Step 3: File Creation\n\n1. Create the `llms.txt` file in the repository root\n2. Follow the exact format specification\n3. Include all required sections\n4. Use proper markdown formatting\n5. Ensure all links are valid relative paths\n\n### Step 4: Validation\n1. Verify compliance with https:\u002F\u002Fllmstxt.org\u002F specification\n2. Check that all links are valid and accessible\n3. Ensure the file serves as an effective LLM navigation tool\n4. Confirm the file is both human and machine readable\n\n## Quality Assurance\n\n### Format Validation\n\n- ✅ H1 header with project name\n- ✅ Blockquote summary (if included)\n- ✅ H2 sections for file lists\n- ✅ Proper markdown link format\n- ✅ No broken or invalid links\n- ✅ Consistent formatting throughout\n\n### Content Validation\n\n- ✅ Clear, unambiguous language\n- ✅ Comprehensive coverage of essential files\n- ✅ Logical organization of content\n- ✅ Appropriate file descriptions\n- ✅ Serves as effective LLM navigation tool\n\n### Specification Compliance\n\n- ✅ Follows https:\u002F\u002Fllmstxt.org\u002F format exactly\n- ✅ Uses required markdown structure\n- ✅ Implements optional sections appropriately\n- ✅ File located at repository root (`\u002Fllms.txt`)\n\n## Example Structure Template\n\n```txt\n# [Repository Name]\n\n> [Concise description of the repository's purpose and scope]\n\n[Optional additional context paragraphs without headings]\n\n## Documentation\n\n- [Main README](README.md): Primary project documentation and getting started guide\n- [Contributing Guide](CONTRIBUTING.md): Guidelines for contributing to the project\n- [Code of Conduct](CODE_OF_CONDUCT.md): Community guidelines and expectations\n\n## Specifications\n\n- [Technical Specification](spec\u002Ftechnical-spec.md): Detailed technical requirements and constraints\n- [API Specification](spec\u002Fapi-spec.md): Interface definitions and data contracts\n\n## Examples\n\n- [Basic Example](examples\u002Fbasic-usage.md): Simple usage demonstration\n- [Advanced Example](examples\u002Fadvanced-usage.md): Complex implementation patterns\n\n## Configuration\n\n- [Setup Guide](docs\u002Fsetup.md): Installation and configuration instructions\n- [Deployment Guide](docs\u002Fdeployment.md): Production deployment guidelines\n\n## Optional\n\n- [Architecture Documentation](docs\u002Farchitecture.md): Detailed system architecture\n- [Design Decisions](docs\u002Fdecisions.md): Historical design decision records\n```\n\n## Success Criteria\n\nThe created `llms.txt` file should:\n1. Enable LLMs to quickly understand the repository's purpose\n2. Provide clear navigation to essential documentation\n3. Follow the official llms.txt specification exactly\n4. Be comprehensive yet concise\n5. Serve both human and machine readers effectively\n6. Include all critical files for project understanding\n7. Use clear, unambiguous language throughout\n8. Organize content logically for easy consumption\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcreate-llms",5360,"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-15 04:42:30",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fawesome-copilot --skill create-llms",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fawesome-copilot --skill create-llms",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill create-llms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-llms\u002FSKILL.md",true,[],[61,96,124,154,187,203],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":75,"publishedAt":31},"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",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":31},"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",[102],{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":31},"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",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[137,138,139,140,141,142,110,80,143,144,145,146,147,148,149,92,150,151,152,153],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":165,"publishedAt":31},"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",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[166,167,168,169,170,171,172,173,174,23,175,176,177,178,179,81,180,181,182,183,184,110,185,186],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":200,"publishedAt":31},"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",[195,196,199],{"categoryNo":162,"categoryName":163,"taxonomyType":70,"taxonomyTypeDesc":71},{"categoryNo":197,"categoryName":198,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[201,107,23,22,202],"resemble detect","identity",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":207,"sourceHtmlUrl":208,"categories":209,"keywords":214,"publishedAt":31},"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",[210,213],{"categoryNo":211,"categoryName":212,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[215,216,217,218,138,82,9,106,219,220,22,221,222,223,224,225,226,227,228,229,230,231,90,232,233,234,235],"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"]