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 generates standardized bug reports documenting behavioral differences between Oracle and PostgreSQL during database migrations. Use it when you need to record defects with clear reproduction steps, root causes, and validation procedures that reference the Oracle baseline as the source of truth.

Generates bug reports using a structured template with status, component, severity, and test references
Documents expected Oracle behavior versus observed PostgreSQL behavior with explicit data-layer nuances
Provides ordered reproduction scenarios with seed data, operations, expected results, and actual results
Identifies root causes specific to Oracle/PostgreSQL behavioral differences (NULL handling, type coercion, collation, sequences, time zones)
Includes validation steps to confirm fixes on both databases
Organizes reports by project with descriptive naming conventions in `.github/oracle-to-postgres-migration/Reports/`

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.Open or create a bug report file at `.github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md`
2.Use the BUG-REPORT-TEMPLATE.md as your starting point
3.Fill in Status (✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS), Component, Test, and Severity fields
4.Document the Problem section comparing Oracle expected behavior to PostgreSQL observed behavior
5.Write the Scenario section with ordered reproduction steps including seed data, operation, expected result, and actual result
6.Explain the Root Cause by identifying the specific Oracle/PostgreSQL behavioral difference
7.Describe the Solution with explicit file paths and any required code changes
8.Add Validation steps to confirm the fix works on both databases

Use cases

Good for

Document a NULL vs. empty-string handling difference discovered during migration testing
Report a sequence or constraint behavior mismatch between Oracle and PostgreSQL
Record a type coercion or collation issue affecting query results
Create a bug report for a stored procedure that behaves differently on PostgreSQL
Track and validate fixes for time-zone or padding discrepancies in migrated data

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
DevOps engineers managing migration projects

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

Should I propose client code changes in the bug report?

Avoid client code changes unless required for correct behavior. When proposing them, document and justify them explicitly in the Solution section.

What should I use as the source of truth for expected behavior?

Oracle is always the source of truth. Frame expected behavior from the Oracle baseline and document how PostgreSQL differs.

What data-layer nuances should I call out?

Explicitly document differences in empty string vs. NULL handling, type coercion strictness, collation, sequence values, time zones, padding, and constraints.

How should I name my bug report file?

Use `.github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md` where ProjectName normalizes spaces to hyphens and DescriptiveSlug is PascalCase (e.g., BUG_REPORT_EmptyStringNullHandling).

What should I include as evidence in the report?

Use minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible. Avoid speculative fixes and stick to existing runtime/language versions.

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 to .github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md where:

{ProjectName} is the project's assembly/folder name with spaces normalized to - (e.g. MyApp.DataAccess)
<DescriptiveSlug> is a short PascalCase identifier describing the defect (e.g., EmptyStringNullHandling, RefCursorUnwrapFailure)