Individual skill

reviewing-oracle-to-postgres-migration

Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting/collations, UNION ALL planner risks, materialized-view refresh requirements, timestamps, concurrent transactions, etc.). Use when planning a database migration, reviewing migration artifacts, or validating that integration tests cover Oracle/PostgreSQL differences.

skills/reviewing-oracle-to-postgres-migration/SKILL.md

Read pinned source

Source commit edbecfa9099c4addae1f500cca1ac067204b30fd

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 40,891
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
github-copilot Repository topic
prompt-engineering Repository topic
hacktoberfest Repository topic
agent-skills Repository topic
agents Repository topic
awesome Repository topic
custom-agents Repository topic
data Derived category
data-databases Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,194 bytes
references/REFERENCE.mddoc · 2,832 bytes
references/empty-strings-handling.mddoc · 2,058 bytes
references/no-data-found-exceptions.mddoc · 2,671 bytes
references/oracle-nvl-decode-functions.mddoc · 2,424 bytes
references/oracle-parentheses-from-clause.mddoc · 4,966 bytes
references/oracle-rownum-pagination.mddoc · 2,163 bytes
references/oracle-sysdate-sequences-dual.mddoc · 3,260 bytes
references/oracle-to-postgres-sorting.mddoc · 2,723 bytes
references/oracle-to-postgres-timestamp-timezone.mddoc · 8,622 bytes
references/oracle-to-postgres-to-char-numeric.mddoc · 4,286 bytes
references/oracle-to-postgres-type-coercion.mddoc · 5,031 bytes
references/postgres-concurrent-transactions.mddoc · 9,628 bytes
references/postgres-materialized-view-refresh.mddoc · 1,406 bytes
references/postgres-refcursor-handling.mddoc · 5,796 bytes
references/postgres-union-all-planner.mddoc · 1,626 bytes

Read excerpt


# 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

1. **Planning** — Before starting migration work on a procedure, trigger, query, or refcursor client. Identify which reference insights apply so risks are addressed up front.
2. **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.