
This does the upfront inventory work when you're migrating a .NET solution from Oracle to Postgres. It scans your solution file, checks each project for Oracle dependencies (NuGet packages, connection strings, OracleConnection references), classifies them as MIGRATE, SKIP, ALREADY_MIGRATED, or TEST_PROJECT, then writes a structured markdown plan to a Reports folder. The real value is creating a parseable artifact that downstream migration skills can consume, so you're not rediscovering project structure every time. It also forces you to confirm the classification and migration order before anything gets written, which prevents surprises when libraries get migrated out of dependency order.
$ npx -y skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan --agent claude-codeInstalls into .claude/skills of the current project.
Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.
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:
Oracle.ManagedDataAccess, Oracle.EntityFrameworkCore (check .csproj and packages.config)appsettings.json, web.config, app.configOracleConnection, OracleCommand, OracleDataReader.github/oracle-to-postgres-migration/DDL/Oracle/ (if present)Sponsors