{"id":"66293dba-fb25-41a3-975b-25f43626a7cc","slug":"creating-oracle-to-postgres-migration-bug-report","kind":"skill","name":"creating-oracle-to-postgres-migration-bug-report","summary":"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 severit","owner":"github","repoUrl":"https://github.com/github/awesome-copilot/tree/HEAD/skills/creating-oracle-to-postgres-migration-bug-report","license":"MIT","licenseTier":"permissive","trust":"official","stars":39994,"match":null,"fewStars":false,"format":"skill","createdAt":null,"addedAt":"2026-10-14T05:10:45.296Z","logoUrl":"https://avatars.githubusercontent.com/u/9919?v=4","linkOnly":false,"collection":{"name":"awesome-copilot","repo":"github/awesome-copilot"},"skillPath":"skills/creating-oracle-to-postgres-migration-bug-report","categories":["databases","developer-tools"],"tags":["ai","github-copilot","prompt-engineering","hacktoberfest","agents","awesome","custom-agents"],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-14T05:10:45.295Z","sample":false,"url":"https://conduits.dev/tools/creating-oracle-to-postgres-migration-bug-report","language":"JavaScript","transports":[],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"> 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# 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/BUG-REPORT-TEMPLATE.md](references/BUG-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 / Medium / High / 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/PostgreSQL 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/language versions; avoid speculative fixes\n\n## Filename Convention\n\nSave bug reports to `.github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md` where:\n- `{ProjectName}` is the project's assembly/folder name with spaces normalized to `-` (e.g. `MyApp.DataAccess`)\n- `<DescriptiveSlug>` is a short PascalCase identifier describing the defect (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`)"}