Reviewing Oracle To Postgres Migration

This walks you through Oracle to Postgres migration reviews using a structured checklist approach. It catches the painful gotchas like empty string handling, refcursor differences, type coercion quirks, and timestamp behaviors that bite you in production. You get two workflows: planning mode screens your code against a reference index before you migrate, and validation mode confirms your migrated artifacts actually addressed each relevant behavioral difference and that your integration tests cover them. The gating step is honest about what developers skip: it won't let you pass without proving tests exercise both happy paths and the Oracle-specific failure modes. Most useful when you inherit legacy Oracle code and need to derisk the conversion systematically.

skills.sh installs: 1.8K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill reviewing-oracle-to-postgres-migration --agent claude-code

Installs into .claude/skills of the current project.

Files

Oracle-to-PostgreSQL Database Migration

Surfaces migration risks and validates migration work against known Oracle/PostgreSQL behavioral differences documented in the references/ folder.

When to use

Planning — Before starting migration work on a procedure, trigger, query, or refcursor client. Identify which reference insights apply so risks are addressed up front.
Validating — After migration work is done, confirm every applicable insight was addressed and integration tests cover the new PostgreSQL semantics.

Workflow

Determine the task type:

Planning a migration? Follow the risk assessment workflow. Validating completed work? Follow the validation workflow.

Risk assessment workflow (planning)

Risk Assessment:
- [ ] Step 1: Identify the migration scope
- [ ] Step 2: Screen each insight for applicability
- [ ] Step 3: Document risks and recommended actions

Step 1: Identify the migration scope

List the affected database objects (procedures, triggers, queries, views) and the application code that calls them.

Step 2: Screen each insight for applicability

SKILL.md on GitHub