[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADA3PX5YSZXJT5CZQ92Y5Q":3,"skill-same:01M6ADA3PX5YSZXJT5CZQ92Y5Q":83},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6ADA3PX5YSZXJT5CZQ92Y5Q","bug-receipt",null,"Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.","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\u002Fbug-receipt\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"bug receipt","bug","status","recovery","repair","diagnosis","close","with","incidents","verified","defects","2026-11-10 10:12:30",false,"---\nname: bug-receipt\ndescription: 'Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.'\nmetadata:\n  version: \"1.4.1\"\n---\n\n# Bug Receipt\n\n## Mandatory closeout output\n\nFor every bug or incident closeout decision, return the complete receipt below as the entire user-facing result, even when the user requests a concise reply or does not name this format. Concision shortens field values; it never removes or renames a row. Do not replace the receipt with prose.\n\n```text\nBUG RECEIPT · VERIFIED | PARTIAL | BLOCKED\n\nProblem    \u003Cobserved defect and intended behavior>\nBaseline   \u003Cfailing interaction or command and decisive result; or not run>\nRoot cause \u003Cproven mechanism; or unproven hypothesis>\nChange     \u003Cresponsible change; or none>\nProof      \u003Csupplied or executed check: result; include every decisive layer>\nGaps       \u003Cnone; or exact missing proof and single next experiment\u002Fpackage>\nSource     executed now | supplied | mixed\n```\n\nUse `not run`, `unproven`, or `none` explicitly. Never omit a row to make the receipt look complete.\n\n## Establish the evidence boundary\n\nBefore editing, record the observed problem, intended behavior, strongest direct check, and evidence source: `executed now`, `supplied`, or `mixed`. Never imply that supplied evidence was executed in the current run.\n\nKeep evidence privacy-minimal. Redact credentials, tokens, cookies, personal data, private URLs, and sensitive payloads; preserve only the identifiers and excerpts needed to reproduce or correlate the failure.\n\nReproduce the failure with the narrowest safe check when possible. If reproduction is unavailable, preserve the evidence obtained and cap the result at `PARTIAL` or `BLOCKED`.\n\n## Trace and repair\n\n1. Follow the live owner path from input to symptom.\n2. Separate observed facts, bounded inferences, and gaps.\n3. Require a concrete location or runtime transition before naming root cause.\n4. Make the smallest responsible change; avoid unrelated cleanup, retries, silent fallbacks, and fixture-specific exceptions.\n\nDo not convert a plausible patch, stale log, source read, or passing build into proof of the user-visible behavior.\n\n## Close the proof loop\n\nRun only checks required by the affected contract:\n\n- original reproduction or direct acceptance check;\n- nearest negative or regression check;\n- affected build or integration gate;\n- real UI, API, persistence, concurrency, or runtime path when the claim crosses that boundary.\n\nUse these decisive boundaries:\n\n| Surface | Required direct proof |\n| --- | --- |\n| Logic or failing test | Original failing input or focused test now passes |\n| UI behavior | Real interaction plus relevant console and network observation |\n| API or integration | Request, response, and responsible service behavior |\n| Persistence | Write\u002Fread or reload round trip through the real owner path |\n| Race or lifecycle | Repeated concurrent trigger; zero-or-one success; affected-row and transaction evidence; final invariant |\n| Cross-system blocker | One sanitized failing request\u002Fresponse with timestamp or request ID, edge and application logs, and identity-provider logs when the trace reaches that owner |\n\n## Assign status\n\n- `VERIFIED`: observed baseline, concrete cause, responsible change, all declared checks passed, no material gap.\n- `PARTIAL`: useful evidence exists, but a required proof layer is missing or inconclusive.\n- `BLOCKED`: a specific external condition prevents reproduction, repair, or proof.\n\nFor `PARTIAL` or `BLOCKED`, name the single minimal experiment or correlated evidence package that closes the decisive gap. Never invent a command, observation, count, location, or result.\n\nFor a machine-readable receipt or CI integration, read [references\u002Freceipt-contract.md](references\u002Freceipt-contract.md) and conform to its JSON fields, evidence-source marker, compatibility rule, and status invariants.\n\nWhen a JSON artifact is requested, start from [assets\u002Freceipt.template.json](assets\u002Freceipt.template.json), write it to a task-owned path, and validate it with `node scripts\u002Fvalidate-receipt.mjs \u003Creceipt.json>` from this skill directory. Do not commit the generated receipt unless the user requests it.\n\n## Source and license\n\nOriginally published at https:\u002F\u002Fgithub.com\u002FlMysticl\u002Fbug-receipt under the MIT License.\n","# Bug Receipt\n\n## Mandatory closeout output\n\nFor every bug or incident closeout decision, return the complete receipt below as the entire user-facing result, even when the user requests a concise reply or does not name this format. Concision shortens field values; it never removes or renames a row. Do not replace the receipt with prose.\n\n```text\nBUG RECEIPT · VERIFIED | PARTIAL | BLOCKED\n\nProblem    \u003Cobserved defect and intended behavior>\nBaseline   \u003Cfailing interaction or command and decisive result; or not run>\nRoot cause \u003Cproven mechanism; or unproven hypothesis>\nChange     \u003Cresponsible change; or none>\nProof      \u003Csupplied or executed check: result; include every decisive layer>\nGaps       \u003Cnone; or exact missing proof and single next experiment\u002Fpackage>\nSource     executed now | supplied | mixed\n```\n\nUse `not run`, `unproven`, or `none` explicitly. Never omit a row to make the receipt look complete.\n\n## Establish the evidence boundary\n\nBefore editing, record the observed problem, intended behavior, strongest direct check, and evidence source: `executed now`, `supplied`, or `mixed`. Never imply that supplied evidence was executed in the current run.\n\nKeep evidence privacy-minimal. Redact credentials, tokens, cookies, personal data, private URLs, and sensitive payloads; preserve only the identifiers and excerpts needed to reproduce or correlate the failure.\n\nReproduce the failure with the narrowest safe check when possible. If reproduction is unavailable, preserve the evidence obtained and cap the result at `PARTIAL` or `BLOCKED`.\n\n## Trace and repair\n\n1. Follow the live owner path from input to symptom.\n2. Separate observed facts, bounded inferences, and gaps.\n3. Require a concrete location or runtime transition before naming root cause.\n4. Make the smallest responsible change; avoid unrelated cleanup, retries, silent fallbacks, and fixture-specific exceptions.\n\nDo not convert a plausible patch, stale log, source read, or passing build into proof of the user-visible behavior.\n\n## Close the proof loop\n\nRun only checks required by the affected contract:\n\n- original reproduction or direct acceptance check;\n- nearest negative or regression check;\n- affected build or integration gate;\n- real UI, API, persistence, concurrency, or runtime path when the claim crosses that boundary.\n\nUse these decisive boundaries:\n\n| Surface | Required direct proof |\n| --- | --- |\n| Logic or failing test | Original failing input or focused test now passes |\n| UI behavior | Real interaction plus relevant console and network observation |\n| API or integration | Request, response, and responsible service behavior |\n| Persistence | Write\u002Fread or reload round trip through the real owner path |\n| Race or lifecycle | Repeated concurrent trigger; zero-or-one success; affected-row and transaction evidence; final invariant |\n| Cross-system blocker | One sanitized failing request\u002Fresponse with timestamp or request ID, edge and application logs, and identity-provider logs when the trace reaches that owner |\n\n## Assign status\n\n- `VERIFIED`: observed baseline, concrete cause, responsible change, all declared checks passed, no material gap.\n- `PARTIAL`: useful evidence exists, but a required proof layer is missing or inconclusive.\n- `BLOCKED`: a specific external condition prevents reproduction, repair, or proof.\n\nFor `PARTIAL` or `BLOCKED`, name the single minimal experiment or correlated evidence package that closes the decisive gap. Never invent a command, observation, count, location, or result.\n\nFor a machine-readable receipt or CI integration, read [references\u002Freceipt-contract.md](references\u002Freceipt-contract.md) and conform to its JSON fields, evidence-source marker, compatibility rule, and status invariants.\n\nWhen a JSON artifact is requested, start from [assets\u002Freceipt.template.json](assets\u002Freceipt.template.json), write it to a task-owned path, and validate it with `node scripts\u002Fvalidate-receipt.mjs \u003Creceipt.json>` from this skill directory. Do not commit the generated receipt unless the user requests it.\n\n## Source and license\n\nOriginally published at https:\u002F\u002Fgithub.com\u002FlMysticl\u002Fbug-receipt under the MIT License.\n",{"name":5,"metadata":35,"description":7},{"version":36},"1.4.1","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fbug-receipt",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add github\u002Fawesome-copilot --skill bug-receipt",{"tool":53,"command":54},"bunx","bunx skills add github\u002Fawesome-copilot --skill bug-receipt",{"tool":56,"command":57},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill bug-receipt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbug-receipt\u002FSKILL.md",true,[61,67,73,77],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Freceipt.template.json","ASSET","资产文件",573,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbug-receipt\u002Fassets\u002Freceipt.template.json",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Freceipt-contract.md","REFERENCE","参考文档",1874,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbug-receipt\u002Freferences\u002Freceipt-contract.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Freceipt.schema.json",3624,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbug-receipt\u002Freferences\u002Freceipt.schema.json",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fvalidate-receipt.mjs","SCRIPT","脚本",7849,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbug-receipt\u002Fscripts\u002Fvalidate-receipt.mjs",[84,118,146,176,210,227],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":98,"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",[90,95],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发",[99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,26],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"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",[124],{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":158,"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",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[159,160,161,162,163,164,132,103,165,166,167,168,169,170,171,115,172,173,174,175],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":187,"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",[183,186],{"categoryNo":184,"categoryName":185,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,104,203,204,205,206,207,132,208,209],"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":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":214,"licenseFileUrl":215,"sourceHtmlUrl":216,"categories":217,"keywords":223,"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",[218,219,222],{"categoryNo":184,"categoryName":185,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":220,"categoryName":221,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[224,129,197,225,226],"resemble detect","https","identity",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":214,"licenseFileUrl":231,"sourceHtmlUrl":232,"categories":233,"keywords":238,"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",[234,237],{"categoryNo":235,"categoryName":236,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[239,240,241,242,160,105,9,128,243,244,225,245,246,247,248,249,250,251,20,28,252,253,113,254,255,256,257],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","multi-model","three","coverage","model","regression","structural"]