Creating Oracle To Postgres Migration Integration Tests
boshi-xixixi/TraeSkill
Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations.
Official agent skill
Creating Oracle To Postgres Migration Integration Tests
by github in github/awesome-copilot
Creates integration test cases targeting Oracle for .NET data access artifacts.
Install Creating Oracle To Postgres Migration Integration Tests
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-integration-tests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creating-oracle-to-postgres-migration-integration-tests .claude/skills/creating-oracle-to-postgres-migration-integration-tests && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "creating-oracle-to-postgres-migration-integration-tests" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests into .claude/skills/creating-oracle-to-postgres-migration-integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-migration-integration-tests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-testsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-integration-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creating-oracle-to-postgres-migration-integration-tests .agents/skills/creating-oracle-to-postgres-migration-integration-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "creating-oracle-to-postgres-migration-integration-tests" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests into .agents/skills/creating-oracle-to-postgres-migration-integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-migration-integration-tests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-integration-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creating-oracle-to-postgres-migration-integration-tests .cursor/skills/creating-oracle-to-postgres-migration-integration-tests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "creating-oracle-to-postgres-migration-integration-tests" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests into .cursor/skills/creating-oracle-to-postgres-migration-integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-migration-integration-tests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/creating-oracle-to-postgres-migration-integration-tests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-integration-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creating-oracle-to-postgres-migration-integration-tests .gemini/skills/creating-oracle-to-postgres-migration-integration-tests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "creating-oracle-to-postgres-migration-integration-tests" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests into .gemini/skills/creating-oracle-to-postgres-migration-integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-migration-integration-tests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-integration-testsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creating-oracle-to-postgres-migration-integration-tests .github/skills/creating-oracle-to-postgres-migration-integration-tests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "creating-oracle-to-postgres-migration-integration-tests" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests into .github/skills/creating-oracle-to-postgres-migration-integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-migration-integration-tests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-integration-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creating-oracle-to-postgres-migration-integration-tests .opencode/skills/creating-oracle-to-postgres-migration-integration-tests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "creating-oracle-to-postgres-migration-integration-tests" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests into .opencode/skills/creating-oracle-to-postgres-migration-integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-migration-integration-tests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
creating-oracle-to-postgres-migration-integration-tests- GitHub stars
- 40k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 508 words
- Files
- 1
- Skills in repo
- 417
- Repo updated
- First seen
- Licence
- MIT
At a glance
Creates integration test cases targeting Oracle for .NET data access artifacts.
- Tasks that involve Integration testing
- SKILL.md covers Prerequisites, Workflow and Key Constraints
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Creating Oracle To Postgres Migration Integration Tests is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Creates integration test cases targeting Oracle for .NET data access artifacts. Tests capture Oracle expected behavior as the authoritative baseline; they are written once and later ported to PostgreSQL by migrating the test project in Phase 6. Use only during Phase 3, before any PostgreSQL migration work has begun. Do not invoke during Phase 6 or against a project that has already been migrated.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Integration testing. It works with PostgreSQL and .NET. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
When your agent uses it
- Tasks that involve Integration testing
Example prompts
- “Use the creating-oracle-to-postgres-migration-integration-tests skill to create integration test cases targeting Oracle for .NET data access artifacts”
- “/creating-oracle-to-postgres-migration-integration-tests”
What it can do on your machine
Read from SKILL.md and the folder at commit 7cce7cf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Creating Oracle To Postgres Migration Integration Tests loads about 1.1k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 508 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from github/awesome-copilot at commit 7cce7cf, republished under its MIT licence (© github). 508 words, ~1,074 tokens.
Download SKILL.mdSave it as
.claude/skills/creating-oracle-to-postgres-migration-integration-tests/SKILL.md (or your agent's skills folder).- name
- creating-oracle-to-postgres-migration-integration-tests
- description
- Creates integration test cases targeting Oracle for .NET data access artifacts. Tests capture Oracle expected behavior as the authoritative baseline; they are written once and later ported to PostgreSQL by migrating the test project in Phase 6. Use only during Phase 3, before any PostgreSQL migration work has begun. Do not invoke during Phase 6 or against a project that has already been migrated.
Creating Integration Tests for Oracle-to-PostgreSQL Migration
Generates integration test cases for data access artifacts in a single target project. Tests target Oracle and capture its behavior as the authoritative baseline. They are written to be logically portable — so they can survive Phase 6 migration without rewriting — but they do not run against PostgreSQL at this stage.
Prerequisites
- The test project must already exist and compile (scaffolded separately).
- Read the existing base test class and seed manager conventions before writing tests.
Workflow
Test Creation:
- [ ] 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 determinismStep 1: Discover the test project conventions
Read the base test class, seed manager, and project file to understand inheritance patterns, transaction management, and seed file conventions.
Step 2: Identify testable data access artifacts
Scope to the target project only. List data access methods that interact with the database — repositories, DAOs, stored procedure callers, query builders.
Step 3: Create seed data
- Follow seed file location and naming conventions from the existing project.
- Avoid
TRUNCATE TABLE— keep existing database data intact. - Assume existing business rows and lookup rows are already present; add only minimal, collision-safe seed records needed for the scenario.
- Do not commit seed data; tests run in transactions that roll back.
- Ensure seed data does not conflict with other tests.
- Load and verify seed data before assertions depend on it.
- Create or reuse a test
LookupConstantsclass for stable lookup IDs/codes used across seed builders and assertions.
Step 4: Write test cases
- Inherit from the base test class to get automatic transaction create/rollback.
- Ensure each database-touching method in scope has at least one integration test (or multiple tests for higher-risk behavior branches).
- Assert logical outputs (rows, columns, counts, error types), not platform-specific messages.
- Assert specific expected values — never assert that a value is merely non-null or non-empty when a concrete value is available from seed data.
- Avoid testing code paths that do not exist or asserting behavior that cannot occur.
- Avoid redundant assertions across tests targeting the same method.
- For text parameters, include both empty-string and
NULL/missing input coverage where applicable. - For datetime behavior, include assertions that validate the value written and read back matches — use the Oracle column's precision (e.g., seconds-only for a date/time column with no fractional seconds) rather than assuming any particular database type syntax.
Show full SKILL.md (138 more words)Show less
Step 5: Review determinism
Re-examine every assertion against non-null values. Confirm each is deterministic against the seeded data. Fix any assertion that depends on database state outside the test's control.
Key Constraints
- Phase 3 only — these tests target Oracle. Do not invoke this skill during Phase 6 or against a PostgreSQL-targeting project.
- Oracle is the golden source — tests capture Oracle's expected behavior.
- Assertion portability — avoid platform-specific error messages or syntax in assertions so that when the test project is migrated to PostgreSQL in Phase 6, assertions require no changes.
- Seed only against Oracle — the test project will be migrated to PostgreSQL in Phase 6; seed data and infrastructure stay Oracle-targeted until then.
- Scoped to one project — do not create tests for artifacts outside the target project.
- Preserve existing data — never rewrite or wipe pre-existing business or lookup rows.
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/creating-oracle-to-postgres-migration-integration-tests of github/awesome-copilot.
Open the folder on GitHubat commit 7cce7cf
Compare with similar skills
Creating Oracle To Postgres Migration Integration Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Creating Oracle To Postgres Migration Integration Tests this skillgithub/awesome-copilot | 40k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Creating Oracle To Postgres Migration Integration Testsboshi-xixixi/TraeSkill | 275 | — | ~760 | Automated safety check: Pass | MIT | |
| Scaffolding Oracle To Postgres Migration Test Projectboshi-xixixi/TraeSkill | 275 | — | ~632 | Automated safety check: Pass | MIT | |
| Integration Tests for pRESTprest/prest | 4.6k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Airbyte Postgres Source E2E Testsairbytehq/airbyte | 22k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| New Event Sourceaws/aws-lambda-dotnet | 1.7k | — | ~3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Scaffolding Oracle To Postgres Migration Test Project
boshi-xixixi/TraeSkill
Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions.
Integration Tests for pREST
prest/prest
Guides writing and reviewing pREST Docker-based integration tests so every HTTP request is explained by step comments or table-driven descriptions.
- Official
Airbyte Postgres Source E2E Tests
airbytehq/airbyte
Starts a local PostgreSQL 16 container, loads SQL fixtures and runs the Airbyte spec, check, discover and read commands against a chosen source-postgres image.
- Official
New Event Source
aws/aws-lambda-dotnet
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
More from github/awesome-copilot
All 417 skills in this repo- Official
Acquire Codebase Knowledge
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
- Official
Draw.io Diagram Generator
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
- Official
Credit Risk Data Cleaning
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
- Official
Daily Focus Board
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
- Official
Python Pypi Package Builder
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Related
Works with
Categories
Questions about Creating Oracle To Postgres Migration Integration Tests
What does Creating Oracle To Postgres Migration Integration Tests do?
Creates integration test cases targeting Oracle for .NET data access artifacts. Creating Oracle To Postgres Migration Integration Tests is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.NET data access artifacts.
When should I use Creating Oracle To Postgres Migration Integration Tests?
Creating Oracle To Postgres Migration Integration Tests fits situations like: tasks that involve Integration testing.
How do I install Creating Oracle To Postgres Migration Integration Tests in Claude Code?
Run `npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a claude-code`. Or copy the skill folder (skills/creating-oracle-to-postgres-migration-integration-tests in github/awesome-copilot) into .claude/skills/creating-oracle-to-postgres-migration-integration-tests in your project. Claude Code loads it when a task matches its description.
How do I install Creating Oracle To Postgres Migration Integration Tests in Codex?
Run `npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a codex`. Or copy the skill folder (skills/creating-oracle-to-postgres-migration-integration-tests in github/awesome-copilot) into .agents/skills/creating-oracle-to-postgres-migration-integration-tests in your project. Codex loads it when a task matches its description.
Can I use Creating Oracle To Postgres Migration Integration Tests in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-oracle-to-postgres-migration-integration-tests, .gemini/skills/creating-oracle-to-postgres-migration-integration-tests, .github/skills/creating-oracle-to-postgres-migration-integration-tests and .opencode/skills/creating-oracle-to-postgres-migration-integration-tests in your project.
What does Creating Oracle To Postgres Migration Integration Tests need to run?
SKILL.md names no scripts, command-line tools or credentials: Creating Oracle To Postgres Migration Integration Tests is instructions for the agent only.
Does Creating Oracle To Postgres Migration Integration Tests access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Creating Oracle To Postgres Migration Integration Tests safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Creating Oracle To Postgres Migration Integration Tests use?
Creating Oracle To Postgres Migration Integration Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Creating Oracle To Postgres Migration Integration Tests use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Creating Oracle To Postgres Migration Integration Tests?
Skills that share tags, products or a category with Creating Oracle To Postgres Migration Integration Tests: Creating Oracle To Postgres Migration Integration Tests (boshi-xixixi/TraeSkill, 275 stars), Scaffolding Oracle To Postgres Migration Test Project (boshi-xixixi/TraeSkill, 275 stars), Integration Tests for pREST (prest/prest, 4.6k stars) and Airbyte Postgres Source E2E Tests (airbytehq/airbyte, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Creating Oracle To Postgres Migration Integration Tests?
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,792 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 8, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.