This walks through a single .NET project and flags every repository, DAO, and service layer method that touches the database, then writes out a structured testing plan focused on Oracle to Postgres migration risks. It's scoped deliberately narrow: one project at a time, database interactions only, with priority given to Oracle-specific features like refcursors and type coercion that tend to break subtly when you switch engines. The output is a markdown file listing what needs tests, what seed data you'll need, and which behavioral differences to watch for. It's honest about the constraints: Oracle is your source of truth, and it assumes you're running side-by-side app instances rather than trying to test both databases through one codebase.
npx -y skills add github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
wshobson/agents
dbt-labs/dbt-agent-skills
github/awesome-copilot