Creating Oracle To Postgres Master Migration Plan — Agent Skill by GitHub

From the author

Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.

— the description by PrimedPaul

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to assessing .NET solutions for Oracle-to-PostgreSQL migration. It scans the solution to identify project dependencies, classifies each project based on its Oracle usage, and produces a standardized migration plan. The output is a structured Markdown file that serves as a roadmap for downstream migration tasks, ensuring that foundational libraries are prioritized correctly.

What it does

Discovers all projects within a .NET solution file.
Scans project files and configurations for Oracle-specific dependencies.
Classifies projects as MIGRATE, SKIP, ALREADY_MIGRATED, or TEST_PROJECT.
Allows user review and adjustment of the generated migration inventory.
Generates a persistent MasterMigrationPlan.md file for tracking progress.
Determines an optimal migration order based on project dependencies.

When to use it

At the start of a multi-project migration from Oracle to PostgreSQL.
When creating an inventory of .NET projects that require database refactoring.
When assessing the scope of Oracle dependencies across a large solution.
To establish a structured migration roadmap for team coordination.

Advantages

Ensures a consistent and repeatable assessment process.
Reduces manual effort in identifying Oracle-dependent codebases.
Provides a machine-readable plan for downstream automation tools.
Promotes logical migration sequencing by prioritizing foundational libraries.

Usage examples

“Create a migration plan for my current .NET solution.”: The agent will scan the solution, classify all projects based on Oracle usage, and present a draft MasterMigrationPlan.md for your review.
“Which projects in my solution need to be migrated to PostgreSQL?”: The agent will identify and list all projects containing Oracle references, categorizing them for your migration inventory.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/github/creating-oracle-to-postgres-master-migration-plan/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip creating-oracle-to-postgres-master-migration-plan.zip -d .agents/skills

Documentation by PrimedPaul

Creating an Oracle-to-PostgreSQL Master Migration Plan

Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.

Workflow

Progress:
- [ ] Step 1: Discover projects in the solution
- [ ] Step 2: Classify each project
- [ ] Step 3: Confirm with user
- [ ] Step 4: Write the plan file

Step 1: Discover projects

Find the Solution File (it has a .sln or .slnx extension) in the workspace root (ask the user if multiple exist). Parse it to extract all .csproj project references. For each project, note the name, path, and type (class library, web API, console, test, etc.).

Step 2: Classify each project

Scan every non-test project for Oracle indicators:

NuGet references: Oracle.ManagedDataAccess, Oracle.EntityFrameworkCore (check .csproj and packages.config)
Config entries: Oracle connection strings in appsettings.json, web.config, app.config
Code usage: OracleConnection, OracleCommand, OracleDataReader
DDL cross-references under .github/oracle-to-postgres-migration/DDL/Oracle/ (if present)

Assign one classification per project:

Classification	Meaning
MIGRATE	Has Oracle interactions requiring conversion
SKIP	No Oracle indicators (UI-only, shared utility, etc.)
ALREADY_MIGRATED	A `-postgres` or `.Postgres` duplicate exists and appears processed
TEST_PROJECT	Test project; handled by the testing workflow

Step 3: Confirm with user

Present the classified list. Let the user adjust classifications or migration ordering before finalizing.

Step 4: Write the plan file

Save to: .github/oracle-to-postgres-migration/Reports/MasterMigrationPlan.md

Use this exact template — downstream consumers depend on the structure:

# Master Migration Plan

**Solution:** {solution file name}
**Solution Root:** {REPOSITORY_ROOT}
**Created:** {timestamp}
**Last Updated:** {timestamp}

## DDL Artifacts

**Location:** {path to DDL artifacts, e.g., `.github/oracle-to-postgres-migration/DDL/`}
**External tool used:** {Yes / No} — {If Yes, name the tool (e.g., `ora2pg`) and note that Phase 4 (Schema & DDL Migration) can be skipped; PostgreSQL DDL artifacts already exist.}

## Solution Summary

| Metric | Count |
|--------|-------|
| Total projects in solution | {n} |
| Projects requiring migration | {n} |
| Projects already migrated | {n} |
| Projects skipped (no Oracle usage) | {n} |
| Test projects (handled separately) | {n} |

## Project Inventory

| # | Project Name | Path | Classification | Notes |
|---|---|---|---|---|
| 1 | {name} | {relative path} | MIGRATE | {notes} |
| 2 | {name} | {relative path} | SKIP | No Oracle dependencies |

## Migration Order

1. **{ProjectName}** — {rationale, e.g., "Core data access library; other projects depend on it."}
2. **{ProjectName}** — {rationale}

Order projects so that shared/foundational libraries are migrated before their dependents.

Files

ATTRIBUTION.mdAdded by AutoGineer935 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md3.4 KiB

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Implement Spec
Matt Pocock· Community
A workflow for implementing technical specifications and tickets using concurrent subagents.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
MCP Builder
AnthropicOfficial
A comprehensive guide for building high-quality Model Context Protocol (MCP) servers to integrate external services with LLMs.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0Low riskHas scriptsGitHub stars of the source repository188.6k
Schema
Corey Haines· Community
Expert guidance for implementing and optimizing JSON-LD schema markup to improve search engine content understanding.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Postgresql Table Design
Seth Hobson· Community
A comprehensive guide for designing, reviewing, and optimizing PostgreSQL database schemas.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
SQL Optimization Patterns
Seth Hobson· Community
A comprehensive guide to optimizing SQL database performance through indexing, query plan analysis, and efficient coding patterns.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
API Scaffolding Fastapi Pro
Seth Hobson· Community
An expert FastAPI developer focused on high-performance, async-first API architecture and production-ready microservices.
Software developmentClaude Code
MITGitHub stars of the source repository42.3k