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).

Files2

2 files · 3.2 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Safety

95

Quality

88

Clarity

90

Completeness

85

Summary

This skill provides a structured template and guidance for creating bug reports documenting behavioral differences during Oracle-to-PostgreSQL migrations. It establishes a standardized format (status, component, severity, root cause, solution, validation) and writing style to ensure migration defects are recorded consistently, with Oracle as the baseline for expected behavior.

Detected Capabilities

file readmarkdown template referencebug report structure guidance

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

oracle to postgres migrationmigration bug reportoracle postgres defectdatabase behavioral differencemigration root cause

Use Cases

Document behavioral differences between Oracle and PostgreSQL during migration
Write migration bug reports with severity classification and reproduction steps
Organize defect tracking across Oracle-to-PostgreSQL projects
Establish root cause analysis for data layer and SQL behavioral mismatches
Create actionable remediation records with validation steps

Quality Notes

Clear, well-structured guidance aligned with agentskills.io specification
Strong scope definition: explicitly focused on Oracle-to-PostgreSQL migration context
Supporting template file is present and well-organized with concrete field definitions
Good emphasis on data layer nuances (empty strings vs NULL, type coercion, collation, sequences, time zones)
Practical filename convention (PascalCase slug) makes bug reports discoverable
Explicit instruction to avoid speculative fixes and stick to existing runtime versions reduces scope creep
Writing style guidelines promote clarity and consistency across teams
Template includes status indicators (✅/⛔/⏳) for at-a-glance triage
Files Modified section encourages traceability back to code changes

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

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