creating-oracle-to-postgres-master-migration-plan

Classifies .NET solution projects for Oracle-to-PostgreSQL migration and writes a master migration plan.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-oracle-to-postgres-master-migration-plan
Source: https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan
Command: npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a multi-project Oracle-to-PostgreSQL migration without a clear inventory leads to missed dependencies and disordered execution. This Skill scans a .NET solution, classifies every project by migration eligibility, and produces a persistent, structured master plan that downstream agents and skills can parse.

Core Features & Use Cases

  • Solution Discovery: Parses .sln or .slnx files to enumerate all .csproj projects with their names, paths, and types.
  • Oracle Dependency Classification: Detects Oracle indicators such as Oracle.ManagedDataAccess NuGet references, Oracle connection strings, and OracleConnection code usage, then assigns MIGRATE, SKIP, ALREADY_MIGRATED, or TEST_PROJECT classifications.
  • Structured Plan Output: Writes a MasterMigrationPlan.md file with a solution summary, project inventory table, and dependency-aware migration ordering.
  • Use Case: A team beginning a database modernization effort runs this Skill on their solution to get a confirmed inventory of which projects contain Oracle dependencies and the order in which to migrate them.

Quick Start

Analyze my .NET solution and create an Oracle-to-PostgreSQL master migration plan classifying every project.

Frequently Asked Questions about creating-oracle-to-postgres-master-migration-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan an Oracle to PostgreSQL migration for a .NET solution?

Start by parsing the .sln or .slnx file to enumerate all projects, then scan each for Oracle indicators like Oracle.ManagedDataAccess references and OracleConnection usage. Classify projects as MIGRATE, SKIP, ALREADY_MIGRATED, or TEST_PROJECT and record the results in a master migration plan.

How to detect which .NET projects use Oracle database dependencies?

Check .csproj and packages.config files for Oracle.ManagedDataAccess or Oracle.EntityFrameworkCore references, scan appsettings.json and web.config for Oracle connection strings, and search code for OracleConnection, OracleCommand, or OracleDataReader usage.

Does this migration planning work with .slnx solution files?

Yes, the workflow supports both .sln and .slnx solution file formats. If multiple solution files exist in the workspace root, the user is asked which one to analyze.

What happens to test projects during Oracle migration planning?

Test projects are classified as TEST_PROJECT and excluded from the main migration ordering. They are handled separately by the testing workflow rather than the standard migration sequence.

Can I adjust project classifications before the migration plan is finalized?

Yes, the workflow includes a confirmation step where the classified project list is presented to the user. You can adjust classifications or migration ordering before the MasterMigrationPlan.md file is written.