Creating Oracle To Postgres Migration Bug Report

If you're migrating from Oracle to Postgres and hitting behavioral differences, this gives you a structured template for documenting them as proper bug reports. It enforces the format: status, severity, reproduction steps, root cause, and validation. The guidance treats Oracle as the source of truth and calls out the usual suspects like empty string vs NULL, type coercion, and collation differences. Honestly, the real value is keeping your team from writing vague bug reports that say "it works in Oracle but not Postgres" without the details anyone needs to actually fix it. Saves as BUG_REPORT_DescriptiveSlug.md and includes a reference template.

skills.sh installs: 1.8K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report --agent claude-code

Installs into .claude/skills of the current project.

Files

Creating Bug Reports for Oracle-to-PostgreSQL Migration

When to Use

Documenting a defect caused by behavioral differences between Oracle and PostgreSQL
Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project

Bug Report Format

Use the template in references/BUG-REPORT-TEMPLATE.md. Each report must include:

Status: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS
Component: Affected endpoint, repository, or stored procedure
Test: Related automated test names
Severity: Low / Medium / High / Critical — based on impact scope
Problem: Expected Oracle behavior vs. observed PostgreSQL behavior
Scenario: Ordered reproduction steps with seed data, operation, expected result, and actual result
Root Cause: The specific Oracle/PostgreSQL behavioral difference causing the defect
Solution: Changes made or required, with explicit file paths
Validation: Steps to confirm the fix on both databases