SkillsAdd

github/awesome-copilot · Official

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.

All-time #6565 First seen Mar 11, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan
View on skills.sh ↗ GitHub repository ↗

Summary

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

azure-storage Same topic
microsoft/azure-skills

Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and D…

567.1K installs
azure-kusto Same topic
microsoft/azure-skills

Query and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetr…

566.2K installs
supabase-postgres-best-practices Same topic
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-database-setup Same topic
prisma/skills

Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…

269.8K installs
prisma-client-api Same topic
prisma/skills

Prisma Client API reference covering model queries, filters, operators, and client methods. Use…

269.3K installs
prisma-cli Same topic
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot
git-commit 44.5K excalidraw-diagram-generator 29.1K documentation-writer 26.2K multi-stage-dockerfile 23.4K prd 22.9K gh-cli 21.9K refactor 21.6K java-springboot 19.9K create-readme 18.1K playwright-generate-test 18K

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,457 B
  • docs SUMMARY.md 372 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,836 installs

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/MasterMigrationPlan.md

Use this exact template — downstream consumers depend on the structure:

````markdown

Master Migration Plan

Solution: {solution file name} Solution Root: {REPOSITORY_ROOT} Created: {timestamp} Last Updated: {timestamp}

DDL Artifacts

Location: {path to DDL artifacts, e.g., .github/oracle-to-postgres-migration/DDL/} External tool used: {Yes / No} — {If Yes, name the tool (e.g., ora2pg) and note that Phase 4 (Schema & DDL Migration) can be skipped; PostgreSQL DDL artifacts already exist.}

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.