[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADM993R44YGEKPE679JNP1":3,"skill-same:01M6ADM993R44YGEKPE679JNP1":74},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6ADM993R44YGEKPE679JNP1","generate-custom-instructions-from-codebase",null,"Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.","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\u002Fgenerate-custom-instructions-from-codebase\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,9,33,34,35,36,37,38],"custom","codebase","generate","generate custom instructions from codebase","instructions","upgrades","for","consistency","generator","project","technology","branches","maintain","version","commits","framework","code","create","copilot","github copilot","2026-11-10 10:12:30",false,"---\nname: generate-custom-instructions-from-codebase\ndescription: 'Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.'\n---\n\n# Migration and Code Evolution Instructions Generator\n\n## Configuration Variables\n\n```\n${MIGRATION_TYPE=\"Framework Version|Architecture Refactoring|Technology Migration|Dependencies Update|Pattern Changes\"}\n\u003C!-- Type of migration or evolution -->\n\n${SOURCE_REFERENCE=\"branch|commit|tag\"}\n\u003C!-- Source reference point (before state) -->\n\n${TARGET_REFERENCE=\"branch|commit|tag\"}  \n\u003C!-- Target reference point (after state) -->\n\n${ANALYSIS_SCOPE=\"Entire project|Specific folder|Modified files only\"}\n\u003C!-- Scope of analysis -->\n\n${CHANGE_FOCUS=\"Breaking Changes|New Conventions|Obsolete Patterns|API Changes|Configuration\"}\n\u003C!-- Main aspect of changes -->\n\n${AUTOMATION_LEVEL=\"Conservative|Balanced|Aggressive\"}\n\u003C!-- Level of automation for Copilot suggestions -->\n\n${GENERATE_EXAMPLES=\"true|false\"}\n\u003C!-- Include transformation examples -->\n\n${VALIDATION_REQUIRED=\"true|false\"}\n\u003C!-- Require validation before application -->\n```\n\n## Generated Prompt\n\n```\n\"Analyze code evolution between two project states to generate precise migration instructions for GitHub Copilot. These instructions will guide Copilot to automatically apply the same transformation patterns during future modifications. Follow this methodology:\n\n### Phase 1: Comparative State Analysis\n\n#### Structural Changes Detection\n- Compare folder structure between ${SOURCE_REFERENCE} and ${TARGET_REFERENCE}\n- Identify moved, renamed, or deleted files\n- Analyze changes in configuration files\n- Document new dependencies and removed ones\n\n#### Code Transformation Analysis\n${MIGRATION_TYPE == \"Framework Version\" ? \n  \"- Identify API changes between framework versions\n   - Analyze new features being used\n   - Document obsolete methods\u002Fproperties\n   - Note syntax or convention changes\" : \"\"}\n\n${MIGRATION_TYPE == \"Architecture Refactoring\" ? \n  \"- Analyze architectural pattern changes\n   - Identify new abstractions introduced\n   - Document responsibility reorganization\n   - Note changes in data flows\" : \"\"}\n\n${MIGRATION_TYPE == \"Technology Migration\" ? \n  \"- Analyze replacement of one technology with another\n   - Identify functional equivalences\n   - Document API and syntax changes\n   - Note new dependencies and configurations\" : \"\"}\n\n#### Transformation Pattern Extraction\n- Identify repetitive transformations applied\n- Analyze conversion rules from old to new format\n- Document exceptions and special cases\n- Create before\u002Fafter correspondence matrix\n\n### Phase 2: Migration Instructions Generation\n\nCreate a `.github\u002Fcopilot-migration-instructions.md` file with this structure:\n\n\\`\\`\\`markdown\n# GitHub Copilot Migration Instructions\n\n## Migration Context\n- **Type**: ${MIGRATION_TYPE}\n- **From**: ${SOURCE_REFERENCE} \n- **To**: ${TARGET_REFERENCE}\n- **Date**: [GENERATION_DATE]\n- **Scope**: ${ANALYSIS_SCOPE}\n\n## Automatic Transformation Rules\n\n### 1. Mandatory Transformations\n${AUTOMATION_LEVEL != \"Conservative\" ? \n  \"[AUTOMATIC_TRANSFORMATION_RULES]\n   - **Old Pattern**: [OLD_CODE]\n   - **New Pattern**: [NEW_CODE]\n   - **Trigger**: When to detect this pattern\n   - **Action**: Transformation to apply automatically\" : \"\"}\n\n### 2. Transformations with Validation\n${VALIDATION_REQUIRED == \"true\" ? \n  \"[TRANSFORMATIONS_WITH_VALIDATION]\n   - **Detected Pattern**: [DESCRIPTION]\n   - **Suggested Transformation**: [NEW_APPROACH]\n   - **Required Validation**: [VALIDATION_CRITERIA]\n   - **Alternatives**: [ALTERNATIVE_OPTIONS]\" : \"\"}\n\n### 3. API Correspondences\n${CHANGE_FOCUS == \"API Changes\" || MIGRATION_TYPE == \"Framework Version\" ? \n  \"[API_CORRESPONDENCE_TABLE]\n   | Old API   | New API   | Notes     | Example        |\n   | --------- | --------- | --------- | -------------- |\n   | [OLD_API] | [NEW_API] | [CHANGES] | [CODE_EXAMPLE] | \" : \"\"} |\n\n### 4. New Patterns to Adopt\n[DETECTED_EMERGING_PATTERNS]\n- **Pattern**: [PATTERN_NAME]\n- **Usage**: [WHEN_TO_USE] \n- **Implementation**: [HOW_TO_IMPLEMENT]\n- **Benefits**: [ADVANTAGES]\n\n### 5. Obsolete Patterns to Avoid\n[DETECTED_OBSOLETE_PATTERNS]\n- **Obsolete Pattern**: [OLD_PATTERN]\n- **Why Avoid**: [REASONS]\n- **Alternative**: [NEW_PATTERN]\n- **Migration**: [CONVERSION_STEPS]\n\n## File Type Specific Instructions\n\n${GENERATE_EXAMPLES == \"true\" ? \n  \"### Configuration Files\n   [CONFIG_TRANSFORMATION_EXAMPLES]\n   \n   ### Main Source Files\n   [SOURCE_TRANSFORMATION_EXAMPLES]\n   \n   ### Test Files\n   [TEST_TRANSFORMATION_EXAMPLES]\" : \"\"}\n\n## Validation and Security\n\n### Automatic Control Points\n- Verifications to perform after each transformation\n- Tests to run to validate changes\n- Performance metrics to monitor\n- Compatibility checks to perform\n\n### Manual Escalation\nSituations requiring human intervention:\n- [COMPLEX_CASES_LIST]\n- [ARCHITECTURAL_DECISIONS]\n- [BUSINESS_IMPACTS]\n\n## Migration Monitoring\n\n### Tracking Metrics\n- Percentage of code automatically migrated\n- Number of manual validations required\n- Error rate of automatic transformations\n- Average migration time per file\n\n### Error Reporting\nHow to report incorrect transformations to Copilot:\n- Feedback patterns to improve rules\n- Exceptions to document\n- Adjustments to make to instructions\n\n\\`\\`\\`\n\n### Phase 3: Contextual Examples Generation\n\n${GENERATE_EXAMPLES == \"true\" ? \n  \"#### Transformation Examples\n   For each identified pattern, generate:\n   \n   \\`\\`\\`\n   \u002F\u002F BEFORE (${SOURCE_REFERENCE})\n   [OLD_CODE_EXAMPLE]\n   \n   \u002F\u002F AFTER (${TARGET_REFERENCE}) \n   [NEW_CODE_EXAMPLE]\n   \n   \u002F\u002F COPILOT INSTRUCTIONS\n   When you see this pattern [TRIGGER], transform it to [NEW_PATTERN] following these steps: [STEPS]\n   \\`\\`\\`\" : \"\"}\n\n### Phase 4: Validation and Optimization\n\n#### Instructions Testing\n- Apply instructions on test code\n- Verify transformation consistency\n- Adjust rules based on results\n- Document exceptions and edge cases\n\n#### Iterative Optimization  \n${AUTOMATION_LEVEL == \"Aggressive\" ? \n  \"- Refine rules to maximize automation\n   - Reduce false positives in detection\n   - Improve transformation accuracy\n   - Document lessons learned\" : \"\"}\n\n### Final Result\n\nMigration instructions that enable GitHub Copilot to:\n1. **Automatically apply** the same transformations during future modifications\n2. **Maintain consistency** with newly adopted conventions  \n3. **Avoid obsolete patterns** by automatically proposing alternatives\n4. **Accelerate future migrations** by capitalizing on acquired experience\n5. **Reduce errors** by automating repetitive transformations\n\nThese instructions transform Copilot into an intelligent migration assistant, capable of reproducing your technology evolution decisions consistently and reliably.\n\"\n```\n\n## Typical Use Cases\n\n### Framework Version Migration\nPerfect for documenting the transition from Angular 14 to Angular 17, React Class Components to Hooks, or .NET Framework to .NET Core. Automatically identifies breaking changes and generates corresponding transformation rules.\n\n### Technology Stack Evolution  \nEssential when replacing a technology entirely: jQuery to React, REST to GraphQL, SQL to NoSQL. Creates a comprehensive migration guide with pattern mappings.\n\n### Architecture Refactoring\nIdeal for large refactorings like Monolith to Microservices, MVC to Clean Architecture, or Component to Composable architecture. Preserves architectural knowledge for future similar transformations.\n\n### Design Pattern Modernization\nUseful for adopting new patterns: Repository Pattern, Dependency Injection, Observer to Reactive Programming. Documents the rationale and implementation differences.\n\n## Unique Benefits\n\n### ? **Artificial Intelligence Enhancement**\nUnlike traditional migration documentation, these instructions \"train\" GitHub Copilot to reproduce your technology evolution decisions automatically during future code modifications.\n\n### ? **Knowledge Capitalization**  \nTransforms specific project experience into reusable rules, avoiding the loss of migration expertise and accelerating future similar transformations.\n\n### ? **Context-Aware Precision**\nInstead of generic advice, generates instructions tailored to your specific codebase, with real before\u002Fafter examples from your project evolution.\n\n### ⚡ **Automated Consistency**\nEnsures that new code additions automatically follow the new conventions, preventing architectural regression and maintaining code evolution coherence.\n","# Migration and Code Evolution Instructions Generator\n\n## Configuration Variables\n\n```\n${MIGRATION_TYPE=\"Framework Version|Architecture Refactoring|Technology Migration|Dependencies Update|Pattern Changes\"}\n\u003C!-- Type of migration or evolution -->\n\n${SOURCE_REFERENCE=\"branch|commit|tag\"}\n\u003C!-- Source reference point (before state) -->\n\n${TARGET_REFERENCE=\"branch|commit|tag\"}  \n\u003C!-- Target reference point (after state) -->\n\n${ANALYSIS_SCOPE=\"Entire project|Specific folder|Modified files only\"}\n\u003C!-- Scope of analysis -->\n\n${CHANGE_FOCUS=\"Breaking Changes|New Conventions|Obsolete Patterns|API Changes|Configuration\"}\n\u003C!-- Main aspect of changes -->\n\n${AUTOMATION_LEVEL=\"Conservative|Balanced|Aggressive\"}\n\u003C!-- Level of automation for Copilot suggestions -->\n\n${GENERATE_EXAMPLES=\"true|false\"}\n\u003C!-- Include transformation examples -->\n\n${VALIDATION_REQUIRED=\"true|false\"}\n\u003C!-- Require validation before application -->\n```\n\n## Generated Prompt\n\n```\n\"Analyze code evolution between two project states to generate precise migration instructions for GitHub Copilot. These instructions will guide Copilot to automatically apply the same transformation patterns during future modifications. Follow this methodology:\n\n### Phase 1: Comparative State Analysis\n\n#### Structural Changes Detection\n- Compare folder structure between ${SOURCE_REFERENCE} and ${TARGET_REFERENCE}\n- Identify moved, renamed, or deleted files\n- Analyze changes in configuration files\n- Document new dependencies and removed ones\n\n#### Code Transformation Analysis\n${MIGRATION_TYPE == \"Framework Version\" ? \n  \"- Identify API changes between framework versions\n   - Analyze new features being used\n   - Document obsolete methods\u002Fproperties\n   - Note syntax or convention changes\" : \"\"}\n\n${MIGRATION_TYPE == \"Architecture Refactoring\" ? \n  \"- Analyze architectural pattern changes\n   - Identify new abstractions introduced\n   - Document responsibility reorganization\n   - Note changes in data flows\" : \"\"}\n\n${MIGRATION_TYPE == \"Technology Migration\" ? \n  \"- Analyze replacement of one technology with another\n   - Identify functional equivalences\n   - Document API and syntax changes\n   - Note new dependencies and configurations\" : \"\"}\n\n#### Transformation Pattern Extraction\n- Identify repetitive transformations applied\n- Analyze conversion rules from old to new format\n- Document exceptions and special cases\n- Create before\u002Fafter correspondence matrix\n\n### Phase 2: Migration Instructions Generation\n\nCreate a `.github\u002Fcopilot-migration-instructions.md` file with this structure:\n\n\\`\\`\\`markdown\n# GitHub Copilot Migration Instructions\n\n## Migration Context\n- **Type**: ${MIGRATION_TYPE}\n- **From**: ${SOURCE_REFERENCE} \n- **To**: ${TARGET_REFERENCE}\n- **Date**: [GENERATION_DATE]\n- **Scope**: ${ANALYSIS_SCOPE}\n\n## Automatic Transformation Rules\n\n### 1. Mandatory Transformations\n${AUTOMATION_LEVEL != \"Conservative\" ? \n  \"[AUTOMATIC_TRANSFORMATION_RULES]\n   - **Old Pattern**: [OLD_CODE]\n   - **New Pattern**: [NEW_CODE]\n   - **Trigger**: When to detect this pattern\n   - **Action**: Transformation to apply automatically\" : \"\"}\n\n### 2. Transformations with Validation\n${VALIDATION_REQUIRED == \"true\" ? \n  \"[TRANSFORMATIONS_WITH_VALIDATION]\n   - **Detected Pattern**: [DESCRIPTION]\n   - **Suggested Transformation**: [NEW_APPROACH]\n   - **Required Validation**: [VALIDATION_CRITERIA]\n   - **Alternatives**: [ALTERNATIVE_OPTIONS]\" : \"\"}\n\n### 3. API Correspondences\n${CHANGE_FOCUS == \"API Changes\" || MIGRATION_TYPE == \"Framework Version\" ? \n  \"[API_CORRESPONDENCE_TABLE]\n   | Old API   | New API   | Notes     | Example        |\n   | --------- | --------- | --------- | -------------- |\n   | [OLD_API] | [NEW_API] | [CHANGES] | [CODE_EXAMPLE] | \" : \"\"} |\n\n### 4. New Patterns to Adopt\n[DETECTED_EMERGING_PATTERNS]\n- **Pattern**: [PATTERN_NAME]\n- **Usage**: [WHEN_TO_USE] \n- **Implementation**: [HOW_TO_IMPLEMENT]\n- **Benefits**: [ADVANTAGES]\n\n### 5. Obsolete Patterns to Avoid\n[DETECTED_OBSOLETE_PATTERNS]\n- **Obsolete Pattern**: [OLD_PATTERN]\n- **Why Avoid**: [REASONS]\n- **Alternative**: [NEW_PATTERN]\n- **Migration**: [CONVERSION_STEPS]\n\n## File Type Specific Instructions\n\n${GENERATE_EXAMPLES == \"true\" ? \n  \"### Configuration Files\n   [CONFIG_TRANSFORMATION_EXAMPLES]\n   \n   ### Main Source Files\n   [SOURCE_TRANSFORMATION_EXAMPLES]\n   \n   ### Test Files\n   [TEST_TRANSFORMATION_EXAMPLES]\" : \"\"}\n\n## Validation and Security\n\n### Automatic Control Points\n- Verifications to perform after each transformation\n- Tests to run to validate changes\n- Performance metrics to monitor\n- Compatibility checks to perform\n\n### Manual Escalation\nSituations requiring human intervention:\n- [COMPLEX_CASES_LIST]\n- [ARCHITECTURAL_DECISIONS]\n- [BUSINESS_IMPACTS]\n\n## Migration Monitoring\n\n### Tracking Metrics\n- Percentage of code automatically migrated\n- Number of manual validations required\n- Error rate of automatic transformations\n- Average migration time per file\n\n### Error Reporting\nHow to report incorrect transformations to Copilot:\n- Feedback patterns to improve rules\n- Exceptions to document\n- Adjustments to make to instructions\n\n\\`\\`\\`\n\n### Phase 3: Contextual Examples Generation\n\n${GENERATE_EXAMPLES == \"true\" ? \n  \"#### Transformation Examples\n   For each identified pattern, generate:\n   \n   \\`\\`\\`\n   \u002F\u002F BEFORE (${SOURCE_REFERENCE})\n   [OLD_CODE_EXAMPLE]\n   \n   \u002F\u002F AFTER (${TARGET_REFERENCE}) \n   [NEW_CODE_EXAMPLE]\n   \n   \u002F\u002F COPILOT INSTRUCTIONS\n   When you see this pattern [TRIGGER], transform it to [NEW_PATTERN] following these steps: [STEPS]\n   \\`\\`\\`\" : \"\"}\n\n### Phase 4: Validation and Optimization\n\n#### Instructions Testing\n- Apply instructions on test code\n- Verify transformation consistency\n- Adjust rules based on results\n- Document exceptions and edge cases\n\n#### Iterative Optimization  \n${AUTOMATION_LEVEL == \"Aggressive\" ? \n  \"- Refine rules to maximize automation\n   - Reduce false positives in detection\n   - Improve transformation accuracy\n   - Document lessons learned\" : \"\"}\n\n### Final Result\n\nMigration instructions that enable GitHub Copilot to:\n1. **Automatically apply** the same transformations during future modifications\n2. **Maintain consistency** with newly adopted conventions  \n3. **Avoid obsolete patterns** by automatically proposing alternatives\n4. **Accelerate future migrations** by capitalizing on acquired experience\n5. **Reduce errors** by automating repetitive transformations\n\nThese instructions transform Copilot into an intelligent migration assistant, capable of reproducing your technology evolution decisions consistently and reliably.\n\"\n```\n\n## Typical Use Cases\n\n### Framework Version Migration\nPerfect for documenting the transition from Angular 14 to Angular 17, React Class Components to Hooks, or .NET Framework to .NET Core. Automatically identifies breaking changes and generates corresponding transformation rules.\n\n### Technology Stack Evolution  \nEssential when replacing a technology entirely: jQuery to React, REST to GraphQL, SQL to NoSQL. Creates a comprehensive migration guide with pattern mappings.\n\n### Architecture Refactoring\nIdeal for large refactorings like Monolith to Microservices, MVC to Clean Architecture, or Component to Composable architecture. Preserves architectural knowledge for future similar transformations.\n\n### Design Pattern Modernization\nUseful for adopting new patterns: Repository Pattern, Dependency Injection, Observer to Reactive Programming. Documents the rationale and implementation differences.\n\n## Unique Benefits\n\n### ? **Artificial Intelligence Enhancement**\nUnlike traditional migration documentation, these instructions \"train\" GitHub Copilot to reproduce your technology evolution decisions automatically during future code modifications.\n\n### ? **Knowledge Capitalization**  \nTransforms specific project experience into reusable rules, avoiding the loss of migration expertise and accelerating future similar transformations.\n\n### ? **Context-Aware Precision**\nInstead of generic advice, generates instructions tailored to your specific codebase, with real before\u002Fafter examples from your project evolution.\n\n### ⚡ **Automated Consistency**\nEnsures that new code additions automatically follow the new conventions, preventing architectural regression and maintaining code evolution coherence.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fgenerate-custom-instructions-from-codebase",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add github\u002Fawesome-copilot --skill generate-custom-instructions-from-codebase",{"tool":60,"command":61},"bunx","bunx skills add github\u002Fawesome-copilot --skill generate-custom-instructions-from-codebase",{"tool":63,"command":64},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill generate-custom-instructions-from-codebase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgenerate-custom-instructions-from-codebase\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002FHasarAli\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot-agents\u002Fskills\u002Fimplement-spec\u002Fagents\u002Fopenai.yaml",[75,109,135,162,196,213],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":89,"publishedAt":39},"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",[81,86],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发",[90,91,92,93,28,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"supabase","rls","supabase rls","supabase rls policies","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":39},"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",[115],{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},[117,118,119,120,121,122,25,123,124,125,126,32,127,128,129,130,131,132,133,134],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":39},"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",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[19,35,148,149,150,151,25,28,152,153,154,155,156,24,157,105,158,159,160,161],"logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","package","apps","Legacy","debugging","workflows",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":39},"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",[169,172],{"categoryNo":170,"categoryName":171,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},[174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,94,189,190,191,192,193,25,194,195],"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":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":200,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":209,"publishedAt":39},"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",[204,205,208],{"categoryNo":170,"categoryName":171,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":206,"categoryName":207,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},[210,120,183,211,212],"resemble detect","https","identity",{"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":200,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":224,"publishedAt":39},"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",[220,223],{"categoryNo":221,"categoryName":222,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},[225,226,227,228,35,95,9,119,229,230,211,231,232,233,234,235,236,237,238,239,240,241,103,242,243,244,245],"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"]