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.
This skill creates structured, actionable bug reports for defects found during Oracle-to-PostgreSQL database migrations. It solves the recurring problem that migration bugs often stem from subtle behavioral differences between the two databases, and those differences are easy to describe vaguely; the skill enforces a consistent report format so each defect is captured with enough precision to reproduce, diagnose, and fix on both systems.
It is built around a reusable bug-report template. Every report must include status (resolved, unresolved, or in progress), the affected component, related automated tests, a severity rating, an expected-Oracle-versus-observed-PostgreSQL problem statement, ordered reproduction steps with seed data, the root-cause behavioral difference, the solution with explicit file paths, and validation steps run against both databases. The guidance treats Oracle as the source of truth for expected behavior and prompts authors to call out common data-layer nuances such as empty string versus NULL, type-coercion strictness, collation, sequence values, time zones, padding, and constraints. It also codifies writing style, favoring plain language, numbered steps, minimal SQL and log excerpts as evidence with sensitive data omitted, and a PascalCase filename convention for saved reports.
The intended users are engineers and QA staff running Oracle-to-PostgreSQL migration projects who need to document behavioral defects or review existing bug reports. It is a lightweight, documentation-focused skill consisting of a SKILL.md and the referenced bug-report template, producing well-structured Markdown reports rather than performing any migration or database operations itself.
When documenting a defect caused by a behavioral difference between Oracle and PostgreSQL, or when writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project.
Status, component, related tests, severity, an expected-Oracle-versus-observed-PostgreSQL problem statement, ordered reproduction steps with seed data, root cause, solution with file paths, and validation on both databases.
Oracle is treated as the source of truth, so expected behavior is framed from the Oracle baseline, and reports must call out data-layer nuances like empty string versus NULL, type coercion, collation, sequences, time zones, padding, and constraints.
Save them as BUG_REPORT_<DescriptiveSlug>.md using a short PascalCase slug, written in plain language with numbered steps and minimal SQL or log excerpts as evidence, omitting sensitive data.
No. It is a documentation template and style guide only; it produces Markdown bug reports and does not connect to or operate on any database.
Quick Setup:
.claude/skills/Repository
github/awesome-copilot