How to use the Oracle-to-PostgreSQL Migration Integration Tests agent skill

What does this skill make the agent do?

The skill guides an AI coding agent to write integration tests for data access artifacts in one target .NET project. These include repositories, DAOs, stored procedure callers and query builders. The tests run against Oracle and record Oracle's behavior as the reference, so they can be ported to PostgreSQL later, when the test project is migrated in Phase 6.

The skill also sets rules for test data. It asks for minimal seed records, forbids truncating tables, asks that seed data not be committed, and requires tests to run in transactions that roll back. It also asks for concrete expected values rather than checks that a result is merely non-null.

How do you install the skill?

Download the ZIP for this skill from this page and unzip it. The skill is a single file named SKILL.md. Put the unzipped skill folder in one of these locations:

Use ~/.claude/skills/ to make the skill available across your projects, or use a project's .claude/skills/ folder to share it with one repository.

You can also upload the skill in the Claude apps. Go to Settings, then Capabilities, then Skills, and upload it there.

• Personal: ~/.claude/skills/
• Project: .claude/skills/ inside your repository
• Claude apps: Settings → Capabilities → Skills

How do you trigger the skill with a natural request?

You do not need a special command. Describe the task in plain language while you are in the Phase 3 window of your migration. The skill's description says it should be used only during Phase 3, before any PostgreSQL migration work has begun, so mention that context in your request.

Good requests name the project and the kind of code you want covered. The agent should read your existing base test class and seed manager before writing anything.

• "We are in Phase 3 of the Oracle to PostgreSQL migration. Write Oracle integration tests for the repositories in the Orders.Data project."
• "Add integration tests for the stored procedure callers in the Billing test project, using our existing base test class and seed manager."
• "Review the DAOs in this project and write Oracle-backed tests for the methods that have no coverage yet."

What does the agent do in each step?

The skill defines a five-step workflow. The agent first reads the test project's conventions, including the base test class, seed manager and project file. It then lists the data access methods in the target project and creates seed data that follows the project's existing naming and location rules.

Next it writes test cases that inherit from the base test class, so transactions are created and rolled back automatically. Finally it reviews each assertion to confirm it is deterministic against the seeded data.

• Step 1: Discover the test project conventions
• Step 2: Identify testable data access artifacts
• Step 3: Create seed data
• Step 4: Write test cases
• Step 5: Review determinism

What are the test-writing rules?

The skill asks the agent to assert logical outputs such as rows, columns, counts and error types, not platform-specific messages. For text parameters it asks for both empty-string and NULL or missing input coverage where that applies. For datetime columns it asks the agent to match the Oracle column's precision rather than assume a particular database type syntax.

The skill also asks for a test LookupConstants class holding stable lookup IDs and codes, so seed builders and assertions share the same values.

• Assert specific expected values, not just non-null or non-empty.
• Keep assertions free of Oracle-only or PostgreSQL-only syntax so they need no changes in Phase 6.
• Do not add redundant assertions across tests for the same method.
• Never wipe or rewrite existing business or lookup rows.

What do you need before you start?

The skill assumes your groundwork is already in place. It will not scaffold a test project. Check these items before you ask for tests.

• A .NET test project that already exists and compiles.
• An existing base test class and seed manager for the agent to follow.
• A running Oracle database for the tests to execute against.

Safety notes: scripts and network

The skill's listed metadata states that it does not run scripts and does not use the network. It consists of a single SKILL.md file. The tests it helps write will still execute against your Oracle database, so run them only against a database you are allowed to use for testing, and review the seed data the agent creates before running it.