creating-oracle-to-postgres-migration-bug-report

github/awesome-copilot

Create structured bug reports for Oracle-to-PostgreSQL migration defects with severity, root cause, and remediation steps.

Source View on skills.sh

What is creating-oracle-to-postgres-migration-bug-report?

This skill helps document behavioral differences between Oracle and PostgreSQL as actionable bug reports. Use it when you encounter defects during migration to produce consistent, well-structured reports with reproduction steps, root cause analysis, and validation procedures.

Generate bug reports using a standardized template with status, component, severity, and test references
Document expected Oracle behavior versus observed PostgreSQL behavior with explicit reproduction scenarios
Identify and explain the specific Oracle/PostgreSQL behavioral differences causing each defect
Provide remediation steps with explicit file paths and validation procedures for both databases
Frame Oracle as the source of truth and call out data layer nuances (NULL handling, type coercion, collation, sequences, time zones)

How to install creating-oracle-to-postgres-migration-bug-report

npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report

Claude Code

Cursor

Windsurf

Cline

How to use creating-oracle-to-postgres-migration-bug-report

1.Identify the behavioral difference between Oracle and PostgreSQL
2.Use the BUG-REPORT-TEMPLATE.md to structure your report
3.Set the Status field (✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS)
4.Document the Component (endpoint, repository, or stored procedure affected)
5.Specify Severity (Low/Medium/High/Critical) based on impact scope
6.Write the Problem section comparing expected Oracle behavior to observed PostgreSQL behavior
7.Create a Scenario section with ordered reproduction steps including seed data, operation, expected result, and actual result
8.Explain the Root Cause as the specific Oracle/PostgreSQL behavioral difference

Use cases

Good for

Document a NULL vs. empty string handling difference between Oracle and PostgreSQL
Report a type coercion or constraint strictness issue discovered during migration testing
Create a bug report for a stored procedure or endpoint behaving differently on PostgreSQL
Track and validate fixes for sequence value, collation, or timezone-related defects
Review and standardize bug reports across an Oracle-to-PostgreSQL migration project

Who it's for

Database migration engineers
QA testers validating Oracle-to-PostgreSQL migrations
Backend developers fixing migration-related defects
Technical leads reviewing migration bug reports

creating-oracle-to-postgres-migration-bug-report FAQ

What should I do if the defect requires client code changes?

Document and justify any client code changes explicitly in the Solution section. Avoid proposing client changes unless required for correct behavior.

How do I determine the severity level for a bug report?

Base severity on impact scope: Low for minor issues, Medium for moderate impact, High for significant functionality loss, and Critical for complete feature failure or data integrity issues.

Should I include sensitive data or large SQL logs in the bug report?

No. Keep SQL excerpts minimal and reproducible, omit sensitive data, and include only the logs necessary as evidence.

What data layer nuances should I call out explicitly?

Document differences in empty string vs. NULL handling, type coercion strictness, collation behavior, sequence values, time zones, padding, and constraint enforcement.

What if I'm unsure whether a behavior is an Oracle or PostgreSQL quirk?

Frame Oracle as the source of truth for expected behavior. If uncertain, research the specific behavioral difference and document it clearly in the Root Cause section.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.

name: creating-oracle-to-postgres-migration-bug-report description: '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.'

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

Oracle-to-PostgreSQL Guidance

Oracle is the source of truth — frame expected behavior from the Oracle baseline
Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints
Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly

Writing Style

Plain language, short sentences, clear next actions
Present or past tense consistently
Bullets and numbered lists for steps and validations
Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible
Stick to existing runtime/language versions; avoid speculative fixes

Filename Convention

Save bug reports as BUG_REPORT_<DescriptiveSlug>.md where <DescriptiveSlug> is a short PascalCase identifier (e.g., EmptyStringNullHandling, RefCursorUnwrapFailure).