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

github/awesome-copilot · updated Apr 8, 2026

$npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan
0 commentsdiscussion
summary

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

skill.md

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.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.655 reviews
  • Luis Bhatia· Dec 24, 2024

    creating-oracle-to-postgres-master-migration-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Shikha Mishra· Dec 20, 2024

    I recommend creating-oracle-to-postgres-master-migration-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Liam Tandon· Dec 20, 2024

    creating-oracle-to-postgres-master-migration-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Olivia Patel· Dec 16, 2024

    creating-oracle-to-postgres-master-migration-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Arjun Farah· Dec 8, 2024

    Registry listing for creating-oracle-to-postgres-master-migration-plan matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sakshi Patil· Nov 19, 2024

    Useful defaults in creating-oracle-to-postgres-master-migration-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Luis Diallo· Nov 15, 2024

    Keeps context tight: creating-oracle-to-postgres-master-migration-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yash Thakker· Nov 11, 2024

    creating-oracle-to-postgres-master-migration-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Charlotte Taylor· Nov 11, 2024

    We added creating-oracle-to-postgres-master-migration-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nikhil Anderson· Nov 7, 2024

    I recommend creating-oracle-to-postgres-master-migration-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 55

1 / 6