New to Claude Skills? Learn how to install them →

github on GitHub

Oracle to PostgreSQL Migration

OfficialFree

Identify migration risks between Oracle and PostgreSQL.

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 Migration does

The Oracle to PostgreSQL Migration skill is designed to assist developers and database administrators in navigating the complexities associated with migrating from Oracle to PostgreSQL. It provides a structured approach to identify potential risks and validate migration efforts by cross-referencing code against known behavioral differences between the two database systems. This is particularly useful in ensuring that migration artifacts are compatible with PostgreSQL's semantics and operational characteristics.

The skill is organized into two main workflows: risk assessment and validation. During the planning phase, users can identify the scope of migration, screen relevant insights from a comprehensive reference index, and document any risks along with recommended actions. This proactive approach allows teams to address potential issues before they become problematic during or after migration.

Once the migration is completed, the validation workflow ensures that all applicable insights have been acknowledged and that integration tests adequately cover both expected and edge-case scenarios. This includes verifying behaviors related to empty strings, refcursors, sorting, timestamps, and more, which are critical for maintaining data integrity and application performance post-migration.

This skill is particularly suited for teams undertaking database migrations who need a reliable way to manage the inherent risks and ensure a smooth transition to PostgreSQL. By following the outlined workflows, users can significantly reduce the likelihood of encountering issues that could affect application functionality or data accuracy after the migration is complete.

When to use it

Use this skill when planning a migration to identify potential risks, or after migration to validate that all differences have been addressed.

When not to use it

This skill is not suitable for migrations involving databases other than Oracle or PostgreSQL, or for scenarios where no migration is taking place.

What you can build with it

Planning a Migration

Before starting a migration, use this skill to assess risks related to specific database objects and prepare accordingly.

Validating Migration Artifacts

After migration, confirm that all insights have been addressed and that integration tests cover necessary scenarios.

Documenting Migration Risks

Utilize the skill to document identified risks and recommended actions for future reference and compliance.

How to install Oracle to PostgreSQL Migration

View source

1. Install with the skills CLI

npx skills add github/awesome-copilot/reviewing-oracle-to-postgres-migration --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

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

Review the reference index in references/REFERENCE.md. For each entry, determine whether the migration scope contains patterns affected by that insight. Read the full reference file only when the insight is potentially relevant.

Step 3: Document risks and recommended actions

For each applicable insight, note the specific risk and the recommended fix pattern from the reference file. Flag any insight that requires a design decision (e.g., whether to preserve Oracle empty-string-as-NULL semantics or adopt PostgreSQL behavior).

Validation workflow (post-migration)

Validation:
- [ ] Step 1: Map the migration artifact
- [ ] Step 2: Cross-check applicable insights
- [ ] Step 3: Verify integration test coverage
- [ ] Step 4: Gate the result

Step 1: Map the migration artifact

Identify the migrated object and summarize the change set.

Step 2: Cross-check applicable insights

For each reference in references/REFERENCE.md, confirm the behavior or test requirement is acknowledged and addressed in the migration work.

Step 3: Verify integration test coverage

Confirm tests exercise both the happy path and the failure scenarios highlighted in applicable insights (exceptions, sorting, UNION ALL behavior/performance risks, refcursor consumption, concurrent transactions, timestamps, materialized-view freshness, etc.).

Step 4: Gate the result

Return a checklist asserting each applicable insight was addressed, migration scripts run, and integration tests pass.

Frequently asked questions about Oracle to PostgreSQL Migration

Similar skills