[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADE0PC219AZVCJKZXTZAWC":3,"skill-same:01M6ADE0PC219AZVCJKZXTZAWC":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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6ADE0PC219AZVCJKZXTZAWC","creating-oracle-to-postgres-migration-bug-report",null,"Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreating-oracle-to-postgres-migration-bug-report\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"bug report","report","oracle","creating oracle to postgres migration bug report","migration","bug","postgres","when","root cause","defects","for","root","with","actionable","as","reports","use","remediation","severity","postgresql","2026-11-10 10:12:30",false,"---\nname: creating-oracle-to-postgres-migration-bug-report\ndescription: 'Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.'\n---\n\n# Creating Bug Reports for Oracle-to-PostgreSQL Migration\n\n## When to Use\n\n- Documenting a defect caused by behavioral differences between Oracle and PostgreSQL\n- Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project\n\n## Bug Report Format\n\nUse the template in [references\u002FBUG-REPORT-TEMPLATE.md](references\u002FBUG-REPORT-TEMPLATE.md). Each report must include:\n\n- **Status**: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS\n- **Component**: Affected endpoint, repository, or stored procedure\n- **Test**: Related automated test names\n- **Severity**: Low \u002F Medium \u002F High \u002F Critical — based on impact scope\n- **Problem**: Expected Oracle behavior vs. observed PostgreSQL behavior\n- **Scenario**: Ordered reproduction steps with seed data, operation, expected result, and actual result\n- **Root Cause**: The specific Oracle\u002FPostgreSQL behavioral difference causing the defect\n- **Solution**: Changes made or required, with explicit file paths\n- **Validation**: Steps to confirm the fix on both databases\n\n## Oracle-to-PostgreSQL Guidance\n\n- **Oracle is the source of truth** — frame expected behavior from the Oracle baseline\n- Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints\n- Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly\n\n## Writing Style\n\n- Plain language, short sentences, clear next actions\n- Present or past tense consistently\n- Bullets and numbered lists for steps and validations\n- Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible\n- Stick to existing runtime\u002Flanguage versions; avoid speculative fixes\n\n## Filename Convention\n\nSave bug reports to `.github\u002Foracle-to-postgres-migration\u002FReports\u002F{ProjectName}\u002FBUG_REPORT_\u003CDescriptiveSlug>.md` where:\n- `{ProjectName}` is the project's assembly\u002Ffolder name with spaces normalized to `-` (e.g. `MyApp.DataAccess`)\n- `\u003CDescriptiveSlug>` is a short PascalCase identifier describing the defect (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`)\n","# Creating Bug Reports for Oracle-to-PostgreSQL Migration\n\n## When to Use\n\n- Documenting a defect caused by behavioral differences between Oracle and PostgreSQL\n- Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project\n\n## Bug Report Format\n\nUse the template in [references\u002FBUG-REPORT-TEMPLATE.md](references\u002FBUG-REPORT-TEMPLATE.md). Each report must include:\n\n- **Status**: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS\n- **Component**: Affected endpoint, repository, or stored procedure\n- **Test**: Related automated test names\n- **Severity**: Low \u002F Medium \u002F High \u002F Critical — based on impact scope\n- **Problem**: Expected Oracle behavior vs. observed PostgreSQL behavior\n- **Scenario**: Ordered reproduction steps with seed data, operation, expected result, and actual result\n- **Root Cause**: The specific Oracle\u002FPostgreSQL behavioral difference causing the defect\n- **Solution**: Changes made or required, with explicit file paths\n- **Validation**: Steps to confirm the fix on both databases\n\n## Oracle-to-PostgreSQL Guidance\n\n- **Oracle is the source of truth** — frame expected behavior from the Oracle baseline\n- Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints\n- Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly\n\n## Writing Style\n\n- Plain language, short sentences, clear next actions\n- Present or past tense consistently\n- Bullets and numbered lists for steps and validations\n- Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible\n- Stick to existing runtime\u002Flanguage versions; avoid speculative fixes\n\n## Filename Convention\n\nSave bug reports to `.github\u002Foracle-to-postgres-migration\u002FReports\u002F{ProjectName}\u002FBUG_REPORT_\u003CDescriptiveSlug>.md` where:\n- `{ProjectName}` is the project's assembly\u002Ffolder name with spaces normalized to `-` (e.g. `MyApp.DataAccess`)\n- `\u003CDescriptiveSlug>` is a short PascalCase identifier describing the defect (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`)\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcreating-oracle-to-postgres-migration-bug-report",5335,"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-11 11:59:04",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add github\u002Fawesome-copilot --skill creating-oracle-to-postgres-migration-bug-report",{"tool":65,"command":66},"bunx","bunx skills add github\u002Fawesome-copilot --skill creating-oracle-to-postgres-migration-bug-report",{"tool":68,"command":69},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill creating-oracle-to-postgres-migration-bug-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreating-oracle-to-postgres-migration-bug-report\u002FSKILL.md",true,[73,79],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"agents\u002Fopenai.yaml","REFERENCE","参考文档",145,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Fagents\u002Fopenai.yaml",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002FBUG-REPORT-TEMPLATE.md",2252,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreating-oracle-to-postgres-migration-bug-report\u002Freferences\u002FBUG-REPORT-TEMPLATE.md",[84,115,142,169,203,220],{"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":44},"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,31,104,105,106,107,108,109,110,38,111,112,40,113,114,36],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","tests","prove","users","functions",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":44},"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",[121],{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[123,124,125,126,127,128,34,129,130,131,132,133,134,135,136,137,138,139,140,141],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":44},"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",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[153,154,155,28,156,157,34,103,158,159,160,161,162,163,164,40,165,166,167,168],"custom","code","logicapps custom code net10 migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":180,"publishedAt":44},"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",[176,179],{"categoryNo":177,"categoryName":178,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},[181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,31,196,197,198,199,200,34,201,202],"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":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":207,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":216,"publishedAt":44},"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",[211,212,215],{"categoryNo":177,"categoryName":178,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":213,"categoryName":214,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[217,126,190,218,219],"resemble detect","https","identity",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":207,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":231,"publishedAt":44},"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",[227,230],{"categoryNo":228,"categoryName":229,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[232,233,234,235,154,104,9,125,236,237,218,25,238,24,239,240,241,242,29,243,244,245,111,246,247,248,249],"playbook","quality playbook","quality","code review","tdd","run","spec","council","engineering","functional","spec audit","verified","multi-model","three","coverage","model","regression","structural"]