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

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

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill creating-oracle-to-postgres-master-migration-plan-ultraviollettnympho
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/ultraviollettnympho/transit-ticket/tree/main/.github/skills/creating-oracle-to-postgres-master-migration-plan
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill creating-oracle-to-postgres-master-migration-plan-ultraviollettnympho

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 work. This Skill scans a .NET solution, classifies every project by migration eligibility, and produces a persistent 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.ManagedDataAccess and Oracle.EntityFrameworkCore NuGet references, Oracle connection strings in config files, and OracleConnection/OracleCommand/OracleDataReader code usage, then assigns MIGRATE, SKIP, ALREADY_MIGRATED, or TEST_PROJECT classifications. - Structured Plan Output: Writes a Master Migration Plan markdown file with a solution summary table, project inventory, and dependency-aware migration ordering. - Use Case: A team beginning a database migration asks the assistant to assess their solution; the Skill inventories 20 projects, flags 6 with Oracle dependencies, and produces an ordered migration plan after user confirmation. ## Quick Start Ask the assistant to analyze the .NET solution in this workspace and create an Oracle-to-PostgreSQL master migration plan listing which projects need migration.

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 order them so foundational libraries migrate first.

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

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

Does this migration planning approach handle test projects?

Test projects are detected during solution parsing and assigned the TEST_PROJECT classification. They are excluded from the main migration ordering because they are handled separately by the testing workflow.

What if a project was already migrated to PostgreSQL?

Projects with a -postgres or .Postgres duplicate that appears processed are classified as ALREADY_MIGRATED. This prevents redundant migration work and keeps the plan focused on remaining projects.

Where is the master migration plan file saved?

The plan is saved to .github/oracle-to-postgres-migration/Reports/Master Migration Plan.md using a fixed template with a solution summary table, project inventory, and migration order so downstream agents can parse it reliably.