Skip to main content
affpapa.org
RU EN
skill GitHub Copilot official · GitHub

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

Creates structured bug reports for Oracle-to-PostgreSQL migration defects. Use it when a database behaviour difference needs a reproducible report with a cause and validation plan.

Install into GitHub Copilot · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report
Open on GitHub

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

This skill writes migration defect reports from references/BUG-REPORT-TEMPLATE.md. A report covers status, affected component, related test, severity, expected Oracle behaviour, observed PostgreSQL behaviour, reproduction scenario, root cause, solution and validation on both databases.

It calls out data-layer differences such as empty strings versus NULL, type coercion, collation, sequence values, time zones, padding and constraints. Oracle is treated as the expected-behaviour baseline, so a PostgreSQL difference needs a clear explanation. Client code changes should be documented and justified when required.

Reports follow .github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md. Keep SQL excerpts and logs reproducible, and remove sensitive data.

What it helps with

  • document an Oracle and PostgreSQL behaviour difference
  • write reproduction steps with seed data
  • identify the database-level cause of a defect
  • record file paths for the required fix
  • validate a fix against both databases

Example prompts for the agent

  • Write a bug report for an Oracle empty-string and PostgreSQL `NULL` difference.
  • Review this migration defect report and add the root cause, reproduction scenario and validation steps.
  • Create a report for a type-coercion defect at `.github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md`.

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

1Skills CLI (Vercel)

npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report

2GitHub CLI

gh skill install github/awesome-copilot creating-oracle-to-postgres-migration-bug-report

3Manually: put the files in place

.github/skills/creating-oracle-to-postgres-migration-bug-report/SKILL.md

From the same set554

The whole set →
git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. GitHub Copilot 47,165installs excalidraw-diagram-generator official github Turn a plain-language description into an Excalidraw diagram. Useful for mapping processes, system structure, and relationships between entities. GitHub Copilot 31,639installs multi-stage-dockerfile official github This skill guides GitHub Copilot in writing multi-stage Dockerfiles for different languages and frameworks. Use it when the final runtime image should contain fewer build dependencies. GitHub Copilot 29,688installs documentation-writer official github Skill that turns the agent into a technical writer following the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Proposes structure before writing. GitHub Copilot 27,757installs prd official github Turns a feature idea into a structured PRD with user stories, technical requirements, and risks. Use it when planning a software feature or an AI-powered one. GitHub Copilot 24,035installs refactor official github This skill reshapes existing code without changing its external behavior. Use it for gradual cleanup of large functions, duplication, weak types, and code smells. GitHub Copilot 22,321installs java-springboot official github Gives GitHub Copilot Spring Boot development practices, from project layout to tests and security. Use it when writing or reviewing Java application code. GitHub Copilot 21,272installs create-readme official github This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code. GitHub Copilot 19,081installs

Similar

scientific-visualization K-Dense-AI Generates and audits publication-ready scientific figures in Matplotlib, Seaborn, and Plotly, focusing on truthful data encoding and accessibility. Claude Code CX Codex Cursor +1 2,400installs cohort-analysis phuryn Analyzes user engagement data by cohorts, tracks retention curves, and recommends follow-up product research. Claude Code CX Codex Cursor +1 2,900installs ab-test-analysis phuryn Evaluates A/B test data, checks statistical significance, and delivers clear ship, extend, or stop recommendations. Claude Code CX Codex Cursor +1 2,900installs pandas-pro https://github.com/Jeffallan Skill for efficient pandas work: data cleaning, aggregation, table joins, time series. Useful if you manipulate DataFrames often and want to skip indexing errors and row loops. Claude Code CX Codex Cursor +1 5,700installs statistical-analysis K-Dense-AI Runs hypothesis tests with assumption checking, effect sizes, and APA-formatted reports. Covers t-tests, ANOVA, correlation, regression, non-parametric and Bayesian methods. Claude Code CX Codex Cursor +1 2,300installs prisma-8 prisma Guides coding agents through data contracts, migrations, and queries in Prisma 8. Use it in projects running @prisma/orm-postgres, @prisma/orm-sqlite, or @prisma/orm-mongo. Claude Code CX Codex Cursor +1 305installs xlsx official anthropics Creates, reads, edits, and converts spreadsheet files. Use it when the requested deliverable is an Excel workbook or another tabular file. Claude Code Claude.ai 187,223installs google-agents-cli-observability official Google This skill guides you through tracing and monitoring AI agents, including ADK agents. Use it when you need to inspect agent execution or monitor a deployed agent. Claude Code CX Codex Cursor +1 509,900installs

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

How do I install creating-oracle-to-postgres-migration-bug-report in GitHub Copilot?

Run npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report. Then use .github/skills/creating-oracle-to-postgres-migration-bug-report/SKILL.md.

What does creating-oracle-to-postgres-migration-bug-report do?

It creates structured bug reports for defects caused by Oracle and PostgreSQL behaviour differences during migration. Reports include severity, root cause, remediation and validation steps.

Which database is the expected-behaviour baseline?

The skill uses Oracle as the source of truth for expected behaviour. PostgreSQL behaviour is recorded as the observed result and compared against that baseline.

Source text

SKILL.md · MIT 
---
name: creating-oracle-to-postgres-migration-bug-report
description: '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.'
---

# 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}/BUG_REPORT_<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`)

© github · MIT · github/awesome-copilot

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor