How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

scaffolding-oracle-to-postgres-migration-test-project - Skill

Name: scaffolding-oracle-to-postgres-migration-test-project
Author: github

Imported from github/awesome-copilot (skills/scaffolding-oracle-to-postgres-migration-test-project/SKILL.md) via skills.sh. Install upstream with npx skills add github/awesome-copilot --skill scaffolding-oracle-to-postgres-migration-test-project. Copyright stays with the author.

Scaffolding an Integration Test Project for Oracle-to-PostgreSQL Migration

Creates a compilable, empty xUnit test project with transaction management and seed data infrastructure for a single target project. Run once per project before writing tests.

Workflow

Progress:
- [ ] Step 1: Inspect the target project
- [ ] Step 2: Create the xUnit test project
- [ ] Step 3: Implement transaction-rollback base class
- [ ] Step 4: Implement seed data manager
- [ ] Step 5: Verify the project compiles

Step 1: Inspect the target project

Read the target project's .csproj to determine the .NET version and existing package references. Match these versions exactly — do not upgrade.

Step 2: Create the xUnit test project

Target the same .NET version as the application under test.
Add NuGet packages for Oracle database connectivity (Oracle.ManagedDataAccess.Core) and xUnit.
Add a project reference to the target project only — no other application projects.
Add an appsettings.json configured for Oracle database connectivity.

Step 3: Implement transaction-rollback base class

Create a base test class that opens a transaction before each test and rolls it back after.
Catch and handle all exceptions to guarantee rollback.
Make the pattern inheritable by all downstream test classes.

Step 4: Implement seed data manager

Create a global seed manager for loading test data within the transaction scope.
Do not commit seed data — transactions roll back after each test.
Do not use TRUNCATE TABLE — preserve existing database data.
Establish a naming convention for seed file location that downstream test creation will follow.

Step 5: Verify the project compiles

Build the test project and confirm it compiles with zero errors before finishing.

Key Constraints

Phase 3 only — this skill scaffolds the Oracle-targeting test project. The PostgreSQL test project (Phase 6) is created by copying and migrating this project; do not run this skill again at that point.
Oracle is the golden behavior source — scaffold for Oracle only, not PostgreSQL.
Keep to existing .NET and C# versions; do not introduce newer language or runtime features.
Output is an empty test project with infrastructure only — no test cases.

Install scaffolding-oracle-to-postgres-migration-test-project and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "github-awesome-copilot-scaffolding-oracle-to-postgres-mi-e67d42", "kind": "skill", "name": "scaffolding-oracle-to-postgres-migration-test-project", "description": "Scaffolds an xUnit integration test project targeting Oracle in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use only during Phase 3, before writing Oracle baseline integration tests. Do not invoke during Phase 6 — the PostgreSQL test project is produced by migrating this project, not by running this skill again.", "publisher": "github", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Scaffolds an xUnit integration test project targeting Oracle in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use only during Phase 3, before writing Oracle baseline integration tests. Do not invoke during Phase 6 — the PostgreSQL test project is produced by migrating this project, not by running this skill again." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/github/awesome-copilot", "path": "skills/scaffolding-oracle-to-postgres-migration-test-project/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/github/awesome-copilot/scaffolding-oracle-to-postgres-migration-test-project", "key": "github/awesome-copilot/skills/scaffolding-oracle-to-postgres-migration-test-project/SKILL.md" } }, "instructions": "# Scaffolding an Integration Test Project for Oracle-to-PostgreSQL Migration\n\nCreates a compilable, empty xUnit test project with transaction management and seed data infrastructure for a single target project. Run once per project before writing tests.\n\n## Workflow\n\n```\nProgress:\n- [ ] Step 1: Inspect the target project\n- [ ] Step 2: Create the xUnit test project\n- [ ] Step 3: Implement transaction-rollback base class\n- [ ] Step 4: Implement seed data manager\n- [ ] Step 5: Verify the project compiles\n```\n\n**Step 1: Inspect the target project**\n\nRead the target project's `.csproj` to determine", "cost": { "context_tokens": 573 } }

scaffolding-oracle-to-postgres-migration-test-project

About

Scaffolding an Integration Test Project for Oracle-to-PostgreSQL Migration

Workflow

Key Constraints

Install scaffolding-oracle-to-postgres-migration-test-project and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews