How do I install the Creating Oracle To Postgres Migration Bug Report skill?

Run npx skillmds@latest add boshi-xixixi/creating-oracle-to-postgres-migration-bug-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Creating Oracle To Postgres Migration Bug Report safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Creating Oracle To Postgres Migration Bug Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Creating Oracle To Postgres Migration Bug Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Creating Oracle To Postgres Migration Bug Report?

boshi-xixixi (@boshi-xixixi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Creating Oracle To Postgres Migration Bug Report by boshi-xixixi

Name: Creating Oracle To Postgres Migration Bug Report
Author: boshi-xixixi

Creating Oracle To Postgres Migration Bug Report

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.

boshi-xixixi Updated Sep 17, 2026

File contents

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

---name: creating-oracle-to-postgres-migration-bug-reportdescription: 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 FormatUse the template in [references/BUG-REPORT-TEMPLATE.md](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 ConventionSave bug reports as `BUG_REPORT_<DescriptiveSlug>.md` where `<DescriptiveSlug>` is a short PascalCase identifier (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`).

Frequently asked questions