[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADNF1NA7HMDXB6QSSB4PG5":3,"skill-same:01M6ADNF1NA7HMDXB6QSSB4PG5":82},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6ADNF1NA7HMDXB6QSSB4PG5","gitmoji",null,"Generates commit messages following the gitmoji convention (https:\u002F\u002Fgitmoji.dev) — picks the right emoji for the intent of the change and writes a well-formed message. Use when asked to \"write a gitmoji commit\", \"add an emoji to my commit message\", \"which gitmoji should I use\", \"gitmoji this change\", or when a project uses gitmoji-style commit messages. Works from a git diff, staged changes, or a plain description of the change. Generates the message only — does not run git commands.","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\u002Fgitmoji\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"write","when","for","my","which","add","commands","project","message","intent","only","diff","change","gitmoji commit","commit messages","messages","https","dev","commit message","git","run","commit","2026-11-10 10:12:30",false,"---\nname: gitmoji\ndescription: 'Generates commit messages following the gitmoji convention (https:\u002F\u002Fgitmoji.dev) — picks the right emoji for the intent of the change and writes a well-formed message. Use when asked to \"write a gitmoji commit\", \"add an emoji to my commit message\", \"which gitmoji should I use\", \"gitmoji this change\", or when a project uses gitmoji-style commit messages. Works from a git diff, staged changes, or a plain description of the change. Generates the message only — does not run git commands.'\nlicense: MIT\n---\n\n# Gitmoji\n\nGenerates commit messages that follow the [gitmoji](https:\u002F\u002Fgitmoji.dev\u002F) convention: every commit starts with an emoji that identifies the intent of the change at a glance. Given a diff, a list of staged files, or a plain description of a change, this skill picks the single most appropriate gitmoji and writes a concise, well-formed commit message around it.\n\nThis skill **only generates the message** — it never runs `git commit` or any other git command. The output is a copyable message for the user to use.\n\n## When to Use This Skill\n\n- User says \"write a gitmoji commit\", \"gitmoji this change\", or \"add an emoji to my commit message\"\n- User asks \"which gitmoji should I use for this?\"\n- User pastes a git diff or describes a change in a project that uses gitmoji-style commit history\n- User wants an expressive, scannable commit history using emojis\n\n**When not to use:** if the project follows plain [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) (`feat:`, `fix:`, ...) without emojis, use the `conventional-commit` or `commit-message-storyteller` skill instead. If unsure which convention the project uses, ask the user to provide recent commit history (for example, the output of `git log --oneline -10`).\n\n## Message Format\n\nThe gitmoji specification:\n\n```\n\u003Cintention> [scope?][:?] \u003Cmessage>\n```\n\n- **intention** — exactly one gitmoji expressing the goal of the commit\n- **scope** *(optional)* — the section of the codebase affected, in parentheses\n- **message** — a brief imperative explanation of the change\n\nExamples:\n\n```\n✨ add multi-tenant support to the billing service\n? (auth) prevent token refresh loop on expired sessions\n♻️ (api): extract pagination logic into shared helper\n```\n\n### Emoji Style: Unicode vs Shortcode\n\nGitmoji supports two equivalent notations:\n\n| Style | Example | When to prefer |\n|-------|---------|----------------|\n| Unicode | `✨ add dark mode` | Default — renders everywhere, shorter subject line |\n| Shortcode | `:sparkles: add dark mode` | Platforms that render shortcodes (GitHub, GitLab) or teams that grep commit logs by code |\n\n**Match the repository's existing history.** If recent commits use `:sparkles:`-style shortcodes, generate shortcodes; otherwise default to unicode emojis.\n\n## How It Works\n\n### Step 1: Understand the Change\n\nWork from whatever the user provides:\n\n1. **A git diff** — read it and identify what changed and why\n2. **A list of staged\u002Fmodified files** — infer intent from file names and paths\n3. **A plain description** — use it directly\n\nIf the intent is genuinely ambiguous (e.g. \"updated auth.js\" could be a fix, a feature, or a refactor), ask one short clarifying question rather than guessing.\n\n### Step 2: Identify the Dominant Intent\n\nDetermine the primary purpose of the change. Common intents and their gitmojis:\n\n| Emoji | Shortcode | Intent |\n|-------|-----------|--------|\n| ✨ | `:sparkles:` | Introduce new features |\n| ? | `:bug:` | Fix a bug |\n| ?️ | `:ambulance:` | Critical hotfix |\n| ? | `:memo:` | Add or update documentation |\n| ♻️ | `:recycle:` | Refactor code (no behavior change) |\n| ✅ | `:white_check_mark:` | Add, update, or pass tests |\n| ⚡️ | `:zap:` | Improve performance |\n| ? | `:art:` | Improve structure \u002F format of the code |\n| ? | `:fire:` | Remove code or files |\n| ?️ | `:lock:` | Fix security or privacy issues |\n| ⬆️ | `:arrow_up:` | Upgrade dependencies |\n| ? | `:wrench:` | Add or update configuration files |\n| ? | `:lipstick:` | Add or update the UI and style files |\n| ? | `:boom:` | Introduce breaking changes |\n| ? | `:rotating_light:` | Fix compiler \u002F linter warnings |\n| ? | `:globe_with_meridians:` | Internationalization and localization |\n\nThis is only the most common subset — **always consult [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the full official list of 75 gitmojis** before settling on one; a more specific emoji often exists (e.g. ? for a trivial fix, ✏️ for a typo, ? for a file move).\n\n### Step 3: Pick Exactly One Emoji\n\nRules for ambiguous cases:\n\n- **Specific beats generic** — a typo fix is ✏️, not ?; moving files is ?, not ♻️; a trivial non-critical fix is ?, not ?\n- **Tests:** ✅ for adding\u002Fupdating passing tests; ? only for intentionally failing tests (e.g. TDD red step)\n- **Fix vs hotfix:** ?️ only for urgent production fixes; everyday bug fixes are ?\n- **Security fix:** ?️ wins over ? when the bug is a security issue\n- **Formatting-only changes:** ? for code structure\u002Fformatting; ? only for UI\u002Fstyle files (CSS, themes)\n- **One emoji per commit** — never stack emojis; if two intents feel equally dominant, see mixed changes below\n\n### Step 4: Write the Message\n\n- Imperative mood: \"add\", \"fix\", \"remove\" — not \"added\" or \"fixes\"\n- Keep the subject line under 72 characters including the emoji\n- Lowercase start, no trailing period\n- Add a scope in parentheses when the project's history uses scopes\n- Add a body (separated by a blank line) only when the *why* is not obvious from the subject\n\n### Step 5: Output\n\nProduce the commit message in a copyable code block, followed by one line explaining why that gitmoji was chosen. Do **not** execute `git commit`.\n\n**Example output:**\n\n```\n? (auth) prevent token refresh loop on expired sessions\n\nExpired sessions triggered a refresh that failed validation and\nre-triggered itself, crashing the app. A recursion guard now aborts\nthe cycle and returns a clean 401.\n```\n\n> **Why ?:** the change corrects incorrect runtime behavior — a bug fix, not urgent enough for ?️.\n\n## Edge Cases\n\n| Situation | How to Handle |\n|-----------|---------------|\n| Mixed changes (e.g. feature + refactor in one diff) | Pick the emoji for the *dominant* intent, and suggest splitting into separate commits if the concerns are unrelated |\n| Breaking change | Use ? as the intention and describe the break in the body |\n| Revert | ⏪️ with a subject referencing the reverted commit |\n| Merge commit | ? `merge branch '\u003Cname>' into \u003Ctarget>` |\n| Initial commit | ? `begin project` |\n| Work in progress | ? with a clear note of what remains |\n| No matching emoji feels right | Re-scan the [full reference](references\u002Fgitmoji-reference.md); if still nothing fits, fall back to the closest generic intent (✨, ?, or ♻️) |\n\n## Quick Reference\n\n```bash\n# Get your staged diff to paste into Copilot\ngit diff --staged\n\n# Check which emoji style the repo already uses\ngit log --oneline -10\n```\n\nSee [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the complete official gitmoji list.\n","# Gitmoji\n\nGenerates commit messages that follow the [gitmoji](https:\u002F\u002Fgitmoji.dev\u002F) convention: every commit starts with an emoji that identifies the intent of the change at a glance. Given a diff, a list of staged files, or a plain description of a change, this skill picks the single most appropriate gitmoji and writes a concise, well-formed commit message around it.\n\nThis skill **only generates the message** — it never runs `git commit` or any other git command. The output is a copyable message for the user to use.\n\n## When to Use This Skill\n\n- User says \"write a gitmoji commit\", \"gitmoji this change\", or \"add an emoji to my commit message\"\n- User asks \"which gitmoji should I use for this?\"\n- User pastes a git diff or describes a change in a project that uses gitmoji-style commit history\n- User wants an expressive, scannable commit history using emojis\n\n**When not to use:** if the project follows plain [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) (`feat:`, `fix:`, ...) without emojis, use the `conventional-commit` or `commit-message-storyteller` skill instead. If unsure which convention the project uses, ask the user to provide recent commit history (for example, the output of `git log --oneline -10`).\n\n## Message Format\n\nThe gitmoji specification:\n\n```\n\u003Cintention> [scope?][:?] \u003Cmessage>\n```\n\n- **intention** — exactly one gitmoji expressing the goal of the commit\n- **scope** *(optional)* — the section of the codebase affected, in parentheses\n- **message** — a brief imperative explanation of the change\n\nExamples:\n\n```\n✨ add multi-tenant support to the billing service\n? (auth) prevent token refresh loop on expired sessions\n♻️ (api): extract pagination logic into shared helper\n```\n\n### Emoji Style: Unicode vs Shortcode\n\nGitmoji supports two equivalent notations:\n\n| Style | Example | When to prefer |\n|-------|---------|----------------|\n| Unicode | `✨ add dark mode` | Default — renders everywhere, shorter subject line |\n| Shortcode | `:sparkles: add dark mode` | Platforms that render shortcodes (GitHub, GitLab) or teams that grep commit logs by code |\n\n**Match the repository's existing history.** If recent commits use `:sparkles:`-style shortcodes, generate shortcodes; otherwise default to unicode emojis.\n\n## How It Works\n\n### Step 1: Understand the Change\n\nWork from whatever the user provides:\n\n1. **A git diff** — read it and identify what changed and why\n2. **A list of staged\u002Fmodified files** — infer intent from file names and paths\n3. **A plain description** — use it directly\n\nIf the intent is genuinely ambiguous (e.g. \"updated auth.js\" could be a fix, a feature, or a refactor), ask one short clarifying question rather than guessing.\n\n### Step 2: Identify the Dominant Intent\n\nDetermine the primary purpose of the change. Common intents and their gitmojis:\n\n| Emoji | Shortcode | Intent |\n|-------|-----------|--------|\n| ✨ | `:sparkles:` | Introduce new features |\n| ? | `:bug:` | Fix a bug |\n| ?️ | `:ambulance:` | Critical hotfix |\n| ? | `:memo:` | Add or update documentation |\n| ♻️ | `:recycle:` | Refactor code (no behavior change) |\n| ✅ | `:white_check_mark:` | Add, update, or pass tests |\n| ⚡️ | `:zap:` | Improve performance |\n| ? | `:art:` | Improve structure \u002F format of the code |\n| ? | `:fire:` | Remove code or files |\n| ?️ | `:lock:` | Fix security or privacy issues |\n| ⬆️ | `:arrow_up:` | Upgrade dependencies |\n| ? | `:wrench:` | Add or update configuration files |\n| ? | `:lipstick:` | Add or update the UI and style files |\n| ? | `:boom:` | Introduce breaking changes |\n| ? | `:rotating_light:` | Fix compiler \u002F linter warnings |\n| ? | `:globe_with_meridians:` | Internationalization and localization |\n\nThis is only the most common subset — **always consult [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the full official list of 75 gitmojis** before settling on one; a more specific emoji often exists (e.g. ? for a trivial fix, ✏️ for a typo, ? for a file move).\n\n### Step 3: Pick Exactly One Emoji\n\nRules for ambiguous cases:\n\n- **Specific beats generic** — a typo fix is ✏️, not ?; moving files is ?, not ♻️; a trivial non-critical fix is ?, not ?\n- **Tests:** ✅ for adding\u002Fupdating passing tests; ? only for intentionally failing tests (e.g. TDD red step)\n- **Fix vs hotfix:** ?️ only for urgent production fixes; everyday bug fixes are ?\n- **Security fix:** ?️ wins over ? when the bug is a security issue\n- **Formatting-only changes:** ? for code structure\u002Fformatting; ? only for UI\u002Fstyle files (CSS, themes)\n- **One emoji per commit** — never stack emojis; if two intents feel equally dominant, see mixed changes below\n\n### Step 4: Write the Message\n\n- Imperative mood: \"add\", \"fix\", \"remove\" — not \"added\" or \"fixes\"\n- Keep the subject line under 72 characters including the emoji\n- Lowercase start, no trailing period\n- Add a scope in parentheses when the project's history uses scopes\n- Add a body (separated by a blank line) only when the *why* is not obvious from the subject\n\n### Step 5: Output\n\nProduce the commit message in a copyable code block, followed by one line explaining why that gitmoji was chosen. Do **not** execute `git commit`.\n\n**Example output:**\n\n```\n? (auth) prevent token refresh loop on expired sessions\n\nExpired sessions triggered a refresh that failed validation and\nre-triggered itself, crashing the app. A recursion guard now aborts\nthe cycle and returns a clean 401.\n```\n\n> **Why ?:** the change corrects incorrect runtime behavior — a bug fix, not urgent enough for ?️.\n\n## Edge Cases\n\n| Situation | How to Handle |\n|-----------|---------------|\n| Mixed changes (e.g. feature + refactor in one diff) | Pick the emoji for the *dominant* intent, and suggest splitting into separate commits if the concerns are unrelated |\n| Breaking change | Use ? as the intention and describe the break in the body |\n| Revert | ⏪️ with a subject referencing the reverted commit |\n| Merge commit | ? `merge branch '\u003Cname>' into \u003Ctarget>` |\n| Initial commit | ? `begin project` |\n| Work in progress | ? with a clear note of what remains |\n| No matching emoji feels right | Re-scan the [full reference](references\u002Fgitmoji-reference.md); if still nothing fits, fall back to the closest generic intent (✨, ?, or ♻️) |\n\n## Quick Reference\n\n```bash\n# Get your staged diff to paste into Copilot\ngit diff --staged\n\n# Check which emoji style the repo already uses\ngit log --oneline -10\n```\n\nSee [`references\u002Fgitmoji-reference.md`](references\u002Fgitmoji-reference.md) for the complete official gitmoji list.\n",{"name":5,"license":15,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fgitmoji",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add github\u002Fawesome-copilot --skill gitmoji",{"tool":62,"command":63},"bunx","bunx skills add github\u002Fawesome-copilot --skill gitmoji",{"tool":65,"command":66},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill gitmoji","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgitmoji\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fgitmoji-reference.md","REFERENCE","参考文档",4693,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgitmoji\u002Freferences\u002Fgitmoji-reference.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"SKILL.md.tmpl","OTHER","其他",13331,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fdesign-shotgun\u002FSKILL.md.tmpl",[83,114,141,171,205,221],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":97,"publishedAt":41},"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",[89,94],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[98,99,100,101,26,20,102,31,103,19,104,105,106,107,108,109,110,111,112,113],"supabase","rls","supabase rls","supabase rls policies","review","read","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":41},"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",[120],{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},[122,123,124,125,126,127,21,128,129,130,131,132,133,134,135,136,137,138,139,140],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":153,"publishedAt":41},"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",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[154,155,156,157,158,159,21,26,160,161,162,163,164,165,166,110,167,168,169,170],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"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":182,"publishedAt":41},"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",[178,181],{"categoryNo":179,"categoryName":180,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,20,198,199,200,201,202,21,203,204],"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":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":218,"publishedAt":41},"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",[213,214,217],{"categoryNo":179,"categoryName":180,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":215,"categoryName":216,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},[219,125,192,35,220],"resemble detect","identity",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":232,"publishedAt":41},"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",[228,231],{"categoryNo":229,"categoryName":230,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},[233,234,235,236,155,102,9,124,237,39,35,238,239,240,241,242,243,244,245,246,247,248,108,249,250,251,252],"playbook","quality playbook","quality","code review","tdd","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]