Catalog
github/creating-oracle-to-postgres-master-migration-plan

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.

global
New~770
v1.0Saved Jun 26, 2026

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/Master Migration Plan.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}

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

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

76/100

Grade

B

Good

Safety

82

Quality

72

Clarity

82

Completeness

64

Summary

Discovers all projects in a .NET solution, scans them for Oracle dependencies (NuGet packages, config entries, code patterns), classifies each for PostgreSQL migration eligibility, and writes a structured master migration plan to a persistent file. The skill guides an agent through solution parsing, dependency classification, user confirmation, and plan document generation.

Detected Capabilities

file readsolution/project file parsingNuGet/config analysiscode pattern scanningfile writestructured document generationuser interaction and confirmation

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

oracle to postgres migrationassess oracle dependenciesmigration inventoryclassify projectsmigration planning

Use Cases

  • Establish a migration inventory for a multi-project .NET solution moving from Oracle to PostgreSQL
  • Assess which .NET projects contain Oracle dependencies and require conversion
  • Create a structured migration roadmap that downstream agents and automation can parse and execute against
  • Prioritize projects by dependency order to guide incremental Oracle-to-PostgreSQL migration
  • Document migration status and classify projects for auditing and planning purposes

Quality Notes

  • Well-structured workflow with clear step-by-step progression (discover → classify → confirm → write)
  • Classification matrix explicitly defined with four meaningful categories and their meanings
  • Output template is precise and structured — downstream consumers can reliably parse the plan
  • Detection strategy is comprehensive: NuGet packages, config files, code patterns, and DDL cross-references are all covered
  • User confirmation step before finalizing plan reduces risk of incorrect classifications
  • File write destination is explicit and project-scoped (.github/oracle-to-postgres-migration/Reports/)
  • Dependency ordering rationale included in migration plan section
  • No edge case guidance provided for solution files with unusual structures (e.g., multi-level solution hierarchies, external project references)
  • No error handling described for malformed .csproj files, missing solution file, or permission issues
  • No guidance on handling projects with both Oracle and PostgreSQL (hybrid state) — only covers ALREADY_MIGRATED as a static check
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Add github/creating-oracle-to-postgres-master-migration-plan to your library

Command Palette

Search for a command to run...