[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADDSDDQ9Y8XC6BGN9P2MT2":3,"skill-same:01M6ADDSDDQ9Y8XC6BGN9P2MT2":71},{"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},"01M6ADDSDDQ9Y8XC6BGN9P2MT2","create-technical-spike",null,"Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41133,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-technical-spike\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"spike","create","create technical spike","technical","documents","development","decisions","implementation","time","critical","for","2026-11-10 10:12:30",false,"---\nname: create-technical-spike\ndescription: 'Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.'\n---\n\n# Create Technical Spike Document\n\nCreate time-boxed technical spike documents for researching critical questions that must be answered before development can proceed. Each spike focuses on a specific technical decision with clear deliverables and timelines.\n\n## Document Structure\n\nCreate individual files in `${input:FolderPath|docs\u002Fspikes}` directory. Name each file using the pattern: `[category]-[short-description]-spike.md` (e.g., `api-copilot-integration-spike.md`, `performance-realtime-audio-spike.md`).\n\n```md\n---\ntitle: \"${input:SpikeTitle}\"\ncategory: \"${input:Category|Technical}\"\nstatus: \"? Not Started\"\npriority: \"${input:Priority|High}\"\ntimebox: \"${input:Timebox|1 week}\"\ncreated: [YYYY-MM-DD]\nupdated: [YYYY-MM-DD]\nowner: \"${input:Owner}\"\ntags: [\"technical-spike\", \"${input:Category|technical}\", \"research\"]\n---\n\n# ${input:SpikeTitle}\n\n## Summary\n\n**Spike Objective:** [Clear, specific question or decision that needs resolution]\n\n**Why This Matters:** [Impact on development\u002Farchitecture decisions]\n\n**Timebox:** [How much time allocated to this spike]\n\n**Decision Deadline:** [When this must be resolved to avoid blocking development]\n\n## Research Question(s)\n\n**Primary Question:** [Main technical question that needs answering]\n\n**Secondary Questions:**\n\n- [Related question 1]\n- [Related question 2]\n- [Related question 3]\n\n## Investigation Plan\n\n### Research Tasks\n\n- [ ] [Specific research task 1]\n- [ ] [Specific research task 2]\n- [ ] [Specific research task 3]\n- [ ] [Create proof of concept\u002Fprototype]\n- [ ] [Document findings and recommendations]\n\n### Success Criteria\n\n**This spike is complete when:**\n\n- [ ] [Specific criteria 1]\n- [ ] [Specific criteria 2]\n- [ ] [Clear recommendation documented]\n- [ ] [Proof of concept completed (if applicable)]\n\n## Technical Context\n\n**Related Components:** [List system components affected by this decision]\n\n**Dependencies:** [What other spikes or decisions depend on resolving this]\n\n**Constraints:** [Known limitations or requirements that affect the solution]\n\n## Research Findings\n\n### Investigation Results\n\n[Document research findings, test results, and evidence gathered]\n\n### Prototype\u002FTesting Notes\n\n[Results from any prototypes, spikes, or technical experiments]\n\n### External Resources\n\n- [Link to relevant documentation]\n- [Link to API references]\n- [Link to community discussions]\n- [Link to examples\u002Ftutorials]\n\n## Decision\n\n### Recommendation\n\n[Clear recommendation based on research findings]\n\n### Rationale\n\n[Why this approach was chosen over alternatives]\n\n### Implementation Notes\n\n[Key considerations for implementation]\n\n### Follow-up Actions\n\n- [ ] [Action item 1]\n- [ ] [Action item 2]\n- [ ] [Update architecture documents]\n- [ ] [Create implementation tasks]\n\n## Status History\n\n| Date   | Status         | Notes                      |\n| ------ | -------------- | -------------------------- |\n| [Date] | ? Not Started | Spike created and scoped   |\n| [Date] | ? In Progress | Research commenced         |\n| [Date] | ? Complete    | [Resolution summary]       |\n\n---\n\n_Last updated: [Date] by [Name]_\n```\n\n## Categories for Technical Spikes\n\n### API Integration\n\n- Third-party API capabilities and limitations\n- Integration patterns and authentication\n- Rate limits and performance characteristics\n\n### Architecture & Design\n\n- System architecture decisions\n- Design pattern applicability\n- Component interaction models\n\n### Performance & Scalability\n\n- Performance requirements and constraints\n- Scalability bottlenecks and solutions\n- Resource utilization patterns\n\n### Platform & Infrastructure\n\n- Platform capabilities and limitations\n- Infrastructure requirements\n- Deployment and hosting considerations\n\n### Security & Compliance\n\n- Security requirements and implementations\n- Compliance constraints\n- Authentication and authorization approaches\n\n### User Experience\n\n- User interaction patterns\n- Accessibility requirements\n- Interface design decisions\n\n## File Naming Conventions\n\nUse descriptive, kebab-case names that indicate the category and specific unknown:\n\n**API\u002FIntegration Examples:**\n\n- `api-copilot-chat-integration-spike.md`\n- `api-azure-speech-realtime-spike.md`\n- `api-vscode-extension-capabilities-spike.md`\n\n**Performance Examples:**\n\n- `performance-audio-processing-latency-spike.md`\n- `performance-extension-host-limitations-spike.md`\n- `performance-webrtc-reliability-spike.md`\n\n**Architecture Examples:**\n\n- `architecture-voice-pipeline-design-spike.md`\n- `architecture-state-management-spike.md`\n- `architecture-error-handling-strategy-spike.md`\n\n## Best Practices for AI Agents\n\n1. **One Question Per Spike:** Each document focuses on a single technical decision or research question\n\n2. **Time-Boxed Research:** Define specific time limits and deliverables for each spike\n\n3. **Evidence-Based Decisions:** Require concrete evidence (tests, prototypes, documentation) before marking as complete\n\n4. **Clear Recommendations:** Document specific recommendations and rationale for implementation\n\n5. **Dependency Tracking:** Identify how spikes relate to each other and impact project decisions\n\n6. **Outcome-Focused:** Every spike must result in an actionable decision or recommendation\n\n## Research Strategy\n\n### Phase 1: Information Gathering\n\n1. **Search existing documentation** using search\u002Ffetch tools\n2. **Analyze codebase** for existing patterns and constraints\n3. **Research external resources** (APIs, libraries, examples)\n\n### Phase 2: Validation & Testing\n\n1. **Create focused prototypes** to test specific hypotheses\n2. **Run targeted experiments** to validate assumptions\n3. **Document test results** with supporting evidence\n\n### Phase 3: Decision & Documentation\n\n1. **Synthesize findings** into clear recommendations\n2. **Document implementation guidance** for development team\n3. **Create follow-up tasks** for implementation\n\n## Tools Usage\n\n- **search\u002FsearchResults:** Research existing solutions and documentation\n- **fetch\u002FgithubRepo:** Analyze external APIs, libraries, and examples\n- **codebase:** Understand existing system constraints and patterns\n- **runTasks:** Execute prototypes and validation tests\n- **editFiles:** Update research progress and findings\n- **vscodeAPI:** Test VS Code extension capabilities and limitations\n\nFocus on time-boxed research that resolves critical technical decisions and unblocks development progress.\n","# Create Technical Spike Document\n\nCreate time-boxed technical spike documents for researching critical questions that must be answered before development can proceed. Each spike focuses on a specific technical decision with clear deliverables and timelines.\n\n## Document Structure\n\nCreate individual files in `${input:FolderPath|docs\u002Fspikes}` directory. Name each file using the pattern: `[category]-[short-description]-spike.md` (e.g., `api-copilot-integration-spike.md`, `performance-realtime-audio-spike.md`).\n\n```md\n---\ntitle: \"${input:SpikeTitle}\"\ncategory: \"${input:Category|Technical}\"\nstatus: \"? Not Started\"\npriority: \"${input:Priority|High}\"\ntimebox: \"${input:Timebox|1 week}\"\ncreated: [YYYY-MM-DD]\nupdated: [YYYY-MM-DD]\nowner: \"${input:Owner}\"\ntags: [\"technical-spike\", \"${input:Category|technical}\", \"research\"]\n---\n\n# ${input:SpikeTitle}\n\n## Summary\n\n**Spike Objective:** [Clear, specific question or decision that needs resolution]\n\n**Why This Matters:** [Impact on development\u002Farchitecture decisions]\n\n**Timebox:** [How much time allocated to this spike]\n\n**Decision Deadline:** [When this must be resolved to avoid blocking development]\n\n## Research Question(s)\n\n**Primary Question:** [Main technical question that needs answering]\n\n**Secondary Questions:**\n\n- [Related question 1]\n- [Related question 2]\n- [Related question 3]\n\n## Investigation Plan\n\n### Research Tasks\n\n- [ ] [Specific research task 1]\n- [ ] [Specific research task 2]\n- [ ] [Specific research task 3]\n- [ ] [Create proof of concept\u002Fprototype]\n- [ ] [Document findings and recommendations]\n\n### Success Criteria\n\n**This spike is complete when:**\n\n- [ ] [Specific criteria 1]\n- [ ] [Specific criteria 2]\n- [ ] [Clear recommendation documented]\n- [ ] [Proof of concept completed (if applicable)]\n\n## Technical Context\n\n**Related Components:** [List system components affected by this decision]\n\n**Dependencies:** [What other spikes or decisions depend on resolving this]\n\n**Constraints:** [Known limitations or requirements that affect the solution]\n\n## Research Findings\n\n### Investigation Results\n\n[Document research findings, test results, and evidence gathered]\n\n### Prototype\u002FTesting Notes\n\n[Results from any prototypes, spikes, or technical experiments]\n\n### External Resources\n\n- [Link to relevant documentation]\n- [Link to API references]\n- [Link to community discussions]\n- [Link to examples\u002Ftutorials]\n\n## Decision\n\n### Recommendation\n\n[Clear recommendation based on research findings]\n\n### Rationale\n\n[Why this approach was chosen over alternatives]\n\n### Implementation Notes\n\n[Key considerations for implementation]\n\n### Follow-up Actions\n\n- [ ] [Action item 1]\n- [ ] [Action item 2]\n- [ ] [Update architecture documents]\n- [ ] [Create implementation tasks]\n\n## Status History\n\n| Date   | Status         | Notes                      |\n| ------ | -------------- | -------------------------- |\n| [Date] | ? Not Started | Spike created and scoped   |\n| [Date] | ? In Progress | Research commenced         |\n| [Date] | ? Complete    | [Resolution summary]       |\n\n---\n\n_Last updated: [Date] by [Name]_\n```\n\n## Categories for Technical Spikes\n\n### API Integration\n\n- Third-party API capabilities and limitations\n- Integration patterns and authentication\n- Rate limits and performance characteristics\n\n### Architecture & Design\n\n- System architecture decisions\n- Design pattern applicability\n- Component interaction models\n\n### Performance & Scalability\n\n- Performance requirements and constraints\n- Scalability bottlenecks and solutions\n- Resource utilization patterns\n\n### Platform & Infrastructure\n\n- Platform capabilities and limitations\n- Infrastructure requirements\n- Deployment and hosting considerations\n\n### Security & Compliance\n\n- Security requirements and implementations\n- Compliance constraints\n- Authentication and authorization approaches\n\n### User Experience\n\n- User interaction patterns\n- Accessibility requirements\n- Interface design decisions\n\n## File Naming Conventions\n\nUse descriptive, kebab-case names that indicate the category and specific unknown:\n\n**API\u002FIntegration Examples:**\n\n- `api-copilot-chat-integration-spike.md`\n- `api-azure-speech-realtime-spike.md`\n- `api-vscode-extension-capabilities-spike.md`\n\n**Performance Examples:**\n\n- `performance-audio-processing-latency-spike.md`\n- `performance-extension-host-limitations-spike.md`\n- `performance-webrtc-reliability-spike.md`\n\n**Architecture Examples:**\n\n- `architecture-voice-pipeline-design-spike.md`\n- `architecture-state-management-spike.md`\n- `architecture-error-handling-strategy-spike.md`\n\n## Best Practices for AI Agents\n\n1. **One Question Per Spike:** Each document focuses on a single technical decision or research question\n\n2. **Time-Boxed Research:** Define specific time limits and deliverables for each spike\n\n3. **Evidence-Based Decisions:** Require concrete evidence (tests, prototypes, documentation) before marking as complete\n\n4. **Clear Recommendations:** Document specific recommendations and rationale for implementation\n\n5. **Dependency Tracking:** Identify how spikes relate to each other and impact project decisions\n\n6. **Outcome-Focused:** Every spike must result in an actionable decision or recommendation\n\n## Research Strategy\n\n### Phase 1: Information Gathering\n\n1. **Search existing documentation** using search\u002Ffetch tools\n2. **Analyze codebase** for existing patterns and constraints\n3. **Research external resources** (APIs, libraries, examples)\n\n### Phase 2: Validation & Testing\n\n1. **Create focused prototypes** to test specific hypotheses\n2. **Run targeted experiments** to validate assumptions\n3. **Document test results** with supporting evidence\n\n### Phase 3: Decision & Documentation\n\n1. **Synthesize findings** into clear recommendations\n2. **Document implementation guidance** for development team\n3. **Create follow-up tasks** for implementation\n\n## Tools Usage\n\n- **search\u002FsearchResults:** Research existing solutions and documentation\n- **fetch\u002FgithubRepo:** Analyze external APIs, libraries, and examples\n- **codebase:** Understand existing system constraints and patterns\n- **runTasks:** Execute prototypes and validation tests\n- **editFiles:** Update research progress and findings\n- **vscodeAPI:** Test VS Code extension capabilities and limitations\n\nFocus on time-boxed research that resolves critical technical decisions and unblocks development progress.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcreate-technical-spike",5354,"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-14 05:37:52",{"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 create-technical-spike",{"tool":51,"command":52},"bunx","bunx skills add github\u002Fawesome-copilot --skill create-technical-spike",{"tool":54,"command":55},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill create-technical-spike","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-technical-spike\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",112,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fgit-guardrails-claude-code\u002Fagents\u002Fopenai.yaml",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fblock-dangerous-git.sh","SCRIPT","脚本",507,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fgit-guardrails-claude-code\u002Fscripts\u002Fblock-dangerous-git.sh",[72,107,134,164,198,215],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":86,"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",[78,83],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"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",[113],{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[115,116,117,118,119,120,29,121,122,123,124,125,126,127,128,129,130,131,132,133],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":146,"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",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[147,148,149,150,151,152,29,91,153,154,155,156,157,158,159,103,160,161,162,163],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":175,"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",[171,174],{"categoryNo":172,"categoryName":173,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,92,191,192,193,194,195,29,196,197],"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":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":202,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":211,"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",[206,207,210],{"categoryNo":172,"categoryName":173,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":208,"categoryName":209,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[212,118,185,213,214],"resemble detect","https","identity",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":202,"licenseFileUrl":219,"sourceHtmlUrl":220,"categories":221,"keywords":226,"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",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":84,"categoryName":85,"taxonomyType":81,"taxonomyTypeDesc":82},[227,228,229,230,148,93,9,117,231,232,213,233,234,235,236,237,238,239,240,241,242,243,101,244,245,246,247],"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"]