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.
Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting/collations, UNION ALL planner risks…
Install Reviewing Oracle To Postgres Migration
$ npx skills add github/awesome-copilot --skill reviewing-oracle-to-postgres-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot reviewing-oracle-to-postgres-migration --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/reviewing-oracle-to-postgres-migration .claude/skills/reviewing-oracle-to-postgres-migration && 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 "reviewing-oracle-to-postgres-migration" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/reviewing-oracle-to-postgres-migration into .claude/skills/reviewing-oracle-to-postgres-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-oracle-to-postgres-migration", 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/reviewing-oracle-to-postgres-migrationType 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 reviewing-oracle-to-postgres-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot reviewing-oracle-to-postgres-migration --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/reviewing-oracle-to-postgres-migration .agents/skills/reviewing-oracle-to-postgres-migration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reviewing-oracle-to-postgres-migration" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/reviewing-oracle-to-postgres-migration into .agents/skills/reviewing-oracle-to-postgres-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-oracle-to-postgres-migration", 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 reviewing-oracle-to-postgres-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot reviewing-oracle-to-postgres-migration --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/reviewing-oracle-to-postgres-migration .cursor/skills/reviewing-oracle-to-postgres-migration && 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 "reviewing-oracle-to-postgres-migration" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/reviewing-oracle-to-postgres-migration into .cursor/skills/reviewing-oracle-to-postgres-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-oracle-to-postgres-migration", 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/reviewing-oracle-to-postgres-migration--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 reviewing-oracle-to-postgres-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot reviewing-oracle-to-postgres-migration --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/reviewing-oracle-to-postgres-migration .gemini/skills/reviewing-oracle-to-postgres-migration && 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 "reviewing-oracle-to-postgres-migration" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/reviewing-oracle-to-postgres-migration into .gemini/skills/reviewing-oracle-to-postgres-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-oracle-to-postgres-migration", 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 reviewing-oracle-to-postgres-migrationInstalls 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 reviewing-oracle-to-postgres-migration -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/reviewing-oracle-to-postgres-migration .github/skills/reviewing-oracle-to-postgres-migration && 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 "reviewing-oracle-to-postgres-migration" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/reviewing-oracle-to-postgres-migration into .github/skills/reviewing-oracle-to-postgres-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-oracle-to-postgres-migration", 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 reviewing-oracle-to-postgres-migration -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 reviewing-oracle-to-postgres-migration --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/reviewing-oracle-to-postgres-migration .opencode/skills/reviewing-oracle-to-postgres-migration && 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 "reviewing-oracle-to-postgres-migration" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/reviewing-oracle-to-postgres-migration into .opencode/skills/reviewing-oracle-to-postgres-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-oracle-to-postgres-migration", 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
reviewing-oracle-to-postgres-migration- GitHub stars
- 40k
- Used in
- 1 other repo
- Token cost
- ~798 tokens
- SKILL.md length
- 295 words
- Files
- 16 (incl. references)
- Skills in repo
- 417
- Repo updated
- First seen
- Licence
- MIT
At a glance
Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting/collations, UNION ALL planner risks…
- Works in 2 steps: Planning — Before starting migration… → Validating — After migration work is…
- Planning a database migration
- SKILL.md covers When to use and Workflow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Reviewing Oracle To Postgres Migration is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting/collations, UNION ALL planner risks, materialized-view refresh requirements, timestamps, concurrent transactions, etc.). Use when planning a database migration, reviewing migration artifacts, or validating that integration tests cover Oracle/PostgreSQL differences.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including reference files (for example `references/REFERENCE.md`, `references/empty-strings-handling.md` and `references/no-data-found-exceptions.md`).
It sits in Databases, covering Database migrations and Integration testing. It works with PostgreSQL. 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 a database migration
- Reviewing migration artifacts
- Validating that integration tests cover Oracle/PostgreSQL differences
Example prompts
- “Use the reviewing-oracle-to-postgres-migration skill to identify Oracle-to-PostgreSQL migration risks by cross-referencing code against known…”
- “/reviewing-oracle-to-postgres-migration”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Planning — Before starting migration work on a procedure, trigger, query, or refcursor client. Identify which reference insights apply so…
- Validating — After migration work is done, confirm every applicable insight was addressed and integration tests cover the new PostgreSQL…
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
Reviewing Oracle To Postgres Migration loads about 798 tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 295 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 727ff2e, republished under its MIT licence (© github). 295 words, ~798 tokens.
Download SKILL.mdSave it as
.claude/skills/reviewing-oracle-to-postgres-migration/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.- name
- reviewing-oracle-to-postgres-migration
- description
- Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting/collations, UNION ALL planner risks, materialized-view refresh requirements, timestamps, concurrent transactions, etc.). Use when planning a database migration, reviewing migration artifacts, or validating that integration tests cover Oracle/PostgreSQL differences.
Oracle-to-PostgreSQL Database Migration
Surfaces migration risks and validates migration work against known Oracle/PostgreSQL behavioral differences documented in the references/ folder.
When to use
- Planning — Before starting migration work on a procedure, trigger, query, or refcursor client. Identify which reference insights apply so risks are addressed up front.
- Validating — After migration work is done, confirm every applicable insight was addressed and integration tests cover the new PostgreSQL semantics.
Workflow
Determine the task type:
Planning a migration? Follow the risk assessment workflow. Validating completed work? Follow the validation workflow.
Risk assessment workflow (planning)
Risk Assessment:
- [ ] Step 1: Identify the migration scope
- [ ] Step 2: Screen each insight for applicability
- [ ] Step 3: Document risks and recommended actionsStep 1: Identify the migration scope
List the affected database objects (procedures, triggers, queries, views) and the application code that calls them.
Step 2: Screen each insight for applicability
Review the reference index in references/REFERENCE.md. For each entry, determine whether the migration scope contains patterns affected by that insight. Read the full reference file only when the insight is potentially relevant.
Step 3: Document risks and recommended actions
For each applicable insight, note the specific risk and the recommended fix pattern from the reference file. Flag any insight that requires a design decision (e.g., whether to preserve Oracle empty-string-as-NULL semantics or adopt PostgreSQL behavior).
Validation workflow (post-migration)
Validation:
- [ ] Step 1: Map the migration artifact
- [ ] Step 2: Cross-check applicable insights
- [ ] Step 3: Verify integration test coverage
- [ ] Step 4: Gate the resultStep 1: Map the migration artifact
Identify the migrated object and summarize the change set.
Step 2: Cross-check applicable insights
For each reference in references/REFERENCE.md, confirm the behavior or test requirement is acknowledged and addressed in the migration work.
Step 3: Verify integration test coverage
Confirm tests exercise both the happy path and the failure scenarios highlighted in applicable insights (exceptions, sorting, UNION ALL behavior/performance risks, refcursor consumption, concurrent transactions, timestamps, materialized-view freshness, etc.).
Step 4: Gate the result
Return a checklist asserting each applicable insight was addressed, migration scripts run, and integration tests pass.
© 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
SKILL.md and 15 other files (references) in skills/reviewing-oracle-to-postgres-migration of github/awesome-copilot.
- SKILL.md
- references/REFERENCE.md
- references/empty-strings-handling.md
- references/no-data-found-exceptions.md
- references/oracle-nvl-decode-functions.md
- references/oracle-parentheses-from-clause.md
- references/oracle-rownum-pagination.md
- references/oracle-sysdate-sequences-dual.md
- references/oracle-to-postgres-sorting.md
- references/oracle-to-postgres-timestamp-timezone.md
- references/oracle-to-postgres-to-char-numeric.md
- references/oracle-to-postgres-type-coercion.md
- references/postgres-concurrent-transactions.md
- references/postgres-materialized-view-refresh.md
- references/postgres-refcursor-handling.md
- references/postgres-union-all-planner.md
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
Reviewing Oracle To Postgres Migration 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 |
|---|---|---|---|---|---|---|
| Reviewing Oracle To Postgres Migration this skillgithub/awesome-copilot | 40k | 1 repos | ~798 | Automated safety check: Pass | MIT | |
| Scaffolding Oracle To Postgres Migration Test Projectboshi-xixixi/TraeSkill | 274 | — | ~632 | Automated safety check: Pass | MIT | |
| Supabase Postgres Best Practicessupabase/agent-skills | 2.7k | 24 repos | ~808 | Automated safety check: Pass | MIT | |
| Saleor Django Migration Rulessaleor/saleor | 23k | — | ~1.6k | Automated safety check: Pass | BSD-3-Clause | |
| Airbyte Postgres Source E2E Testsairbytehq/airbyte | 22k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Migrationgocronx-team/gocron | 808 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Supabase Postgres Best Practices
supabase/agent-skills
Gives the agent Postgres rules to consult before writing or changing tables, queries, indexes, RLS policies or migrations, and when diagnosing slow queries.
Saleor Django Migration Rules
saleor/saleor
Rules for writing Django migrations in Saleor that avoid long table locks and stay compatible with zero-downtime rolling deploys.
- 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.
Migration
gocronx-team/gocron
Create, review, or verify gocron database migrations across SQLite, MySQL, and PostgreSQL.
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…
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 Reviewing Oracle To Postgres Migration
What does Reviewing Oracle To Postgres Migration do?
Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting/collations, UNION ALL planner risks…. Reviewing Oracle To Postgres Migration is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.).
When should I use Reviewing Oracle To Postgres Migration?
Reviewing Oracle To Postgres Migration fits situations like: planning a database migration; reviewing migration artifacts; validating that integration tests cover Oracle/PostgreSQL differences.
How do I install Reviewing Oracle To Postgres Migration in Claude Code?
Run `npx skills add github/awesome-copilot --skill reviewing-oracle-to-postgres-migration -a claude-code`. Or copy the skill folder (skills/reviewing-oracle-to-postgres-migration in github/awesome-copilot) into .claude/skills/reviewing-oracle-to-postgres-migration in your project. Claude Code loads it when a task matches its description.
How do I install Reviewing Oracle To Postgres Migration in Codex?
Run `npx skills add github/awesome-copilot --skill reviewing-oracle-to-postgres-migration -a codex`. Or copy the skill folder (skills/reviewing-oracle-to-postgres-migration in github/awesome-copilot) into .agents/skills/reviewing-oracle-to-postgres-migration in your project. Codex loads it when a task matches its description.
Can I use Reviewing Oracle To Postgres Migration 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 reviewing-oracle-to-postgres-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reviewing-oracle-to-postgres-migration, .gemini/skills/reviewing-oracle-to-postgres-migration, .github/skills/reviewing-oracle-to-postgres-migration and .opencode/skills/reviewing-oracle-to-postgres-migration in your project.
What does Reviewing Oracle To Postgres Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Reviewing Oracle To Postgres Migration is instructions for the agent only.
Does Reviewing Oracle To Postgres Migration 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 Reviewing Oracle To Postgres Migration 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 Reviewing Oracle To Postgres Migration use?
Reviewing Oracle To Postgres Migration 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 Reviewing Oracle To Postgres Migration use?
About 798 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.
What are the alternatives to Reviewing Oracle To Postgres Migration?
Skills that share tags, products or a category with Reviewing Oracle To Postgres Migration: Scaffolding Oracle To Postgres Migration Test Project (boshi-xixixi/TraeSkill, 274 stars), Supabase Postgres Best Practices (supabase/agent-skills, 2.7k stars), Saleor Django Migration Rules (saleor/saleor, 23k 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 Reviewing Oracle To Postgres Migration?
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.