New to Claude Skills? Learn how to install them →

Get Claude Skills
github on GitHub

Oracle to PostgreSQL Bug Reporting

OfficialFree

Streamline bug reporting for Oracle-to-PostgreSQL migrations.

by github37.7k stars on github/awesome-copilot
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Oracle to PostgreSQL Bug Reporting does

The Oracle to PostgreSQL Bug Reporting skill provides a structured approach for documenting defects encountered during migrations from Oracle to PostgreSQL. It is particularly useful for developers and database administrators who need to track behavioral differences between the two systems and create actionable bug reports. The skill emphasizes clarity and consistency, ensuring that all relevant details are captured in a standardized format.

Using the provided template, users can create comprehensive bug reports that include essential information such as the status of the bug, the affected components, and the severity of the issue. Each report is designed to clearly outline the expected behavior based on Oracle's functionality compared to what is observed in PostgreSQL. This structured format helps teams quickly identify and address issues, facilitating smoother migration processes.

The guidance within the skill also highlights key differences between Oracle and PostgreSQL that may lead to defects, such as handling of NULL values, type coercion, and constraints. By framing expected behavior from the Oracle baseline, users can better understand the nuances that may impact their applications. The skill encourages minimal changes to client code unless absolutely necessary, promoting a focus on database-level adjustments instead.

Overall, this skill is aimed at teams involved in Oracle-to-PostgreSQL migration projects who require a systematic method for documenting and resolving issues that arise during the transition. It helps ensure that all stakeholders have a clear understanding of the problems and the steps needed to remediate them.

When to use it

Use this skill when you need to document defects caused by behavioral differences between Oracle and PostgreSQL during migration projects.

When not to use it

This skill is not suitable for general bug reporting outside of Oracle-to-PostgreSQL migrations or for projects not involving these databases.

What you can build with it

Documenting a Migration Defect

When a behavioral difference is identified during migration, use the skill to create a detailed bug report.

Reviewing Migration Reports

Team leads can utilize the structured format to review and assess the severity of reported defects.

Tracking Resolution Steps

Use the skill to document the steps taken to resolve defects, ensuring all changes are clear and reproducible.

How to install Oracle to PostgreSQL Bug Reporting

View source

1. Install with the skills CLI

npx skills add github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by github

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

Frequently asked questions about Oracle to PostgreSQL Bug Reporting

Similar skills

Markdown to HTML Conversion

Efficiently convert Markdown documents to HTML.

Code Tour

Create structured walkthroughs for codebases.

Acquire Codebase Knowledge

Streamline onboarding with comprehensive codebase documentation.

Documentation & Modernization

Streamline codebase documentation and modernization planning.

Azure Resource Visualizer

Generate architecture diagrams for Azure resources.

CLAUDE.md Improver

Optimize your CLAUDE.md files for better project context.