SkillsAdd

github/awesome-copilot · Official

creating-oracle-to-postgres-migration-bug-report

Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.

All-time #6593 First seen Mar 11, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

xlsx Shared topics
anthropics/skills

Use this skill any time a spreadsheet file is the primary input or output. This means any task …

165K installs
clerk-setup Shared topics
clerk/skills 42.6K installs
cloudflare-one-migrations Similar name
cloudflare/skills

Assess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, includi…

48K installs
sanity-migration Similar name
sanity-io/agent-toolkit

Plans, implements, and reviews migrations from other CMSes and content systems into Sanity.

16.1K installs
claude-opus-4-5-migration Similar name
anthropics/claude-code

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when …

10.7K installs
react-native-brownfield-migration Similar name
callstackincubator/agent-skills

Implements an accepted incremental brownfield migration from native iOS or Android to React Nat…

4.1K installs

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot
git-commit 44.5K excalidraw-diagram-generator 29.1K documentation-writer 26.2K multi-stage-dockerfile 23.4K prd 22.9K gh-cli 21.9K refactor 21.6K java-springboot 19.9K create-readme 18.1K playwright-generate-test 18K

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,472 B
  • docs SUMMARY.md 293 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,827 installs

SKILL.md

Creating Bug Reports for Oracle-to-PostgreSQL Migration

When to Use

  • Documenting a defect caused by behavioral differences between Oracle and PostgreSQL
  • Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project

Bug Report Format

Use the template in [references/BUG-REPORT-TEMPLATE.md](references/BUG-REPORT-TEMPLATE.md). Each report must include:

  • Status: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS
  • Component: Affected endpoint, repository, or stored procedure
  • Test: Related automated test names
  • Severity: Low / Medium / High / Critical — based on impact scope
  • Problem: Expected Oracle behavior vs. observed PostgreSQL behavior
  • Scenario: Ordered reproduction steps with seed data, operation, expected result, and actual result
  • Root Cause: The specific Oracle/PostgreSQL behavioral difference causing the defect
  • Solution: Changes made or required, with explicit file paths
  • Validation: Steps to confirm the fix on both databases

Oracle-to-PostgreSQL Guidance

  • Oracle is the source of truth — frame expected behavior from the Oracle baseline
  • Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints
  • Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly

Writing Style

  • Plain language, short sentences, clear next actions
  • Present or past tense consistently
  • Bullets and numbered lists for steps and validations
  • Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible
  • Stick to existing runtime/language versions; avoid speculative fixes

Filename Convention

Save bug reports to .github/oracle-to-postgres-migration/Reports/{ProjectName}/BUGREPORT<DescriptiveSlug>.md where:

  • {ProjectName} is the project's assembly/folder name with spaces normalized to - (e.g. MyApp.DataAccess)
  • <DescriptiveSlug> is a short PascalCase identifier describing the defect (e.g., EmptyStringNullHandling, RefCursorUnwrapFailure)