New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Planning Oracle To Postgres Migration Integration Testing

by github in github/awesome-copilot

Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations.

OfficialMITAuto-check passedTesting & QA

Install Planning Oracle To Postgres Migration Integration Testing

skills CLI
$ npx skills add github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot planning-oracle-to-postgres-migration-integration-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/planning-oracle-to-postgres-migration-integration-testing .claude/skills/planning-oracle-to-postgres-migration-integration-testing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
planning-oracle-to-postgres-migration-integration-testing
GitHub stars
40k
Used in
1 other repo
Token cost
~669 tokens
SKILL.md length
245 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations.

  • Planning integration test coverage for a migrated project
  • SKILL.md covers Workflow, Output and Key Constraints
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Identifying which data access methods need tests

What it does

Planning Oracle To Postgres Migration Integration Testing is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.

Its SKILL.md is about 670 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, GitHub 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

  • Planning integration test coverage for a migrated project
  • Identifying which data access methods need tests
  • Preparing for Oracle-to-PostgreSQL migration validation

Example prompts

  • “Use the planning-oracle-to-postgres-migration-integration-testing skill to create an integration testing plan for .NET data access artifacts during…”
  • “/planning-oracle-to-postgres-migration-integration-testing”

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. 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

Planning Oracle To Postgres Migration Integration Testing loads about 669 tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 245 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~126
When it runs · the whole SKILL.md, loaded when a task matches
~669

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 727ff2e, republished under its MIT licence (© github). 245 words, ~669 tokens.

Download SKILL.mdSave it as .claude/skills/planning-oracle-to-postgres-migration-integration-testing/SKILL.md (or your agent's skills folder).
name
planning-oracle-to-postgres-migration-integration-testing
description
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.

Planning Integration Testing for Oracle-to-PostgreSQL Migration

Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan.

Workflow

Progress:
- [ ] Step 1: Identify data access artifacts
- [ ] Step 2: Classify testing priorities
- [ ] Step 3: Write the testing plan

Step 1: Identify data access artifacts

Scope to the target project only. Find classes and methods that interact directly with the database — repositories, DAOs, stored procedure callers, service layers performing CRUD operations.

Step 2: Classify testing priorities

Rank artifacts by migration risk. Prioritize methods that use Oracle-specific features (refcursors, TO_CHAR, implicit type coercion, NO_DATA_FOUND) over simple CRUD.

Step 3: Write the testing plan

Write a markdown plan covering:

  • List of testable artifacts with method signatures
  • Recommended test cases per artifact
  • Seed data requirements
  • Known Oracle→PostgreSQL behavioral differences to validate
  • Coverage mapping that ensures every database touchpoint has at least one test case (or a justified set of cases for high-risk methods)

When defining recommended test cases, explicitly include:

  • Text parameter behavior for both empty string and NULL/missing values.
  • Datetime/timezone assertions, including round-trip and comparison behavior.
  • Cases where destination columns use timestamp without time zone or timestamp(0), with explicit timezone-application expectations.

Output

Write the plan to: .github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md

Key Constraints

  • Single project scope — only plan tests for artifacts within the target project.
  • Database interactions only — skip business logic that does not touch the database.
  • Oracle is the golden source — tests should capture Oracle's expected behavior for comparison against PostgreSQL.
  • No multi-connection harnessing — migrated applications are copied and renamed (e.g., MyApp.Postgres), so each instance targets one database.

© 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/planning-oracle-to-postgres-migration-integration-testing of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Planning Oracle To Postgres Migration Integration Testing 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.

Planning Oracle To Postgres Migration Integration Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Planning Oracle To Postgres Migration Integration Testing this skillgithub/awesome-copilot40k1 repos~669Automated safety check: PassMIT
Creating Oracle To Postgres Migration Integration Testsboshi-xixixi/TraeSkill274—~760Automated safety check: PassMIT
Scaffolding Oracle To Postgres Migration Test Projectboshi-xixixi/TraeSkill274—~632Automated safety check: PassMIT
Airbyte Postgres Source E2E Testsairbytehq/airbyte22k—~2.5kAutomated safety check: PassCustom licence
Pglock Integrationcirello-io/pglock122—~2.2kAutomated safety check: PassApache-2.0
Postgres CDC E2E Test Harnessairbytehq/airbyte22k—~1.9kAutomated safety check: PassCustom licence

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.

    274 GitHub stars~632 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • Airbyte Postgres Source E2E Tests

    airbytehq/airbyte

    Official

    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.

    22k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Pglock Integration

    cirello-io/pglock

    A skill your agent uses when building or modifying a Go application that uses cirello.io/pglock for PostgreSQL-backed distributed locks, per-resource mutual exclusion, leader election, leases…

    122 GitHub stars~2.2k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Postgres CDC E2E Test Harness

    airbytehq/airbyte

    Official

    Reproduces PostgreSQL logical-decoding CDC behavior for Airbyte's source-postgres connector on a local backend, with CDC fixtures, a catalog and smoke case scripts.

    22k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

  • cargo-pgrx Commands and Tests

    yugabyte/yugabyte-db

    Helps choose and run cargo-pgrx commands and decide whether a Rust test is a plain test or a pg_test, so code never crosses the Postgres boundary the wrong way.

    11k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    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.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    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.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Planning Oracle To Postgres Migration Integration Testing

What does Planning Oracle To Postgres Migration Integration Testing do?

Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Planning Oracle To Postgres Migration Integration Testing is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.NET data access artifacts during Oracle-to-PostgreSQL database migrations.

When should I use Planning Oracle To Postgres Migration Integration Testing?

Planning Oracle To Postgres Migration Integration Testing fits situations like: planning integration test coverage for a migrated project; identifying which data access methods need tests; preparing for Oracle-to-PostgreSQL migration validation.

How do I install Planning Oracle To Postgres Migration Integration Testing in Claude Code?

Run `npx skills add github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing -a claude-code`. Or copy the skill folder (skills/planning-oracle-to-postgres-migration-integration-testing in github/awesome-copilot) into .claude/skills/planning-oracle-to-postgres-migration-integration-testing in your project. Claude Code loads it when a task matches its description.

How do I install Planning Oracle To Postgres Migration Integration Testing in Codex?

Run `npx skills add github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing -a codex`. Or copy the skill folder (skills/planning-oracle-to-postgres-migration-integration-testing in github/awesome-copilot) into .agents/skills/planning-oracle-to-postgres-migration-integration-testing in your project. Codex loads it when a task matches its description.

Can I use Planning Oracle To Postgres Migration Integration Testing 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 planning-oracle-to-postgres-migration-integration-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-oracle-to-postgres-migration-integration-testing, .gemini/skills/planning-oracle-to-postgres-migration-integration-testing, .github/skills/planning-oracle-to-postgres-migration-integration-testing and .opencode/skills/planning-oracle-to-postgres-migration-integration-testing in your project.

What does Planning Oracle To Postgres Migration Integration Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Planning Oracle To Postgres Migration Integration Testing is instructions for the agent only.

Does Planning Oracle To Postgres Migration Integration Testing 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 Planning Oracle To Postgres Migration Integration Testing 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 Planning Oracle To Postgres Migration Integration Testing use?

Planning Oracle To Postgres Migration Integration Testing 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 Planning Oracle To Postgres Migration Integration Testing use?

About 669 tokens (SKILL.md is roughly 2.7k 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 Planning Oracle To Postgres Migration Integration Testing?

Skills that share tags, products or a category with Planning Oracle To Postgres Migration Integration Testing: Creating Oracle To Postgres Migration Integration Tests (boshi-xixixi/TraeSkill, 274 stars), Scaffolding Oracle To Postgres Migration Test Project (boshi-xixixi/TraeSkill, 274 stars), Airbyte Postgres Source E2E Tests (airbytehq/airbyte, 22k stars) and Pglock Integration (cirello-io/pglock, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Planning Oracle To Postgres Migration Integration Testing?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 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.