Agent skill · product strategy · github
creating-oracle-to-postgres-master-migration-plan
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.
Why this skill is useful
Adds a detailed executable workflow for classifying .NET projects and generating a structured migration plan that isn't available in public documentation.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 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.) ALREADYMIGRATED A -postgres or .Postgres duplicate exists and appears processed TESTPROJECT 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: ` Order projects so that shared/foundational libraries are migrated before their dependents.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/creating-oracle-to-postgres-master-migration-plan