skilld
All skills
github avatar

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

@f7e8aaa official
by githubgithub/awesome-copilot40k stars
5,040

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report

This session only. Nothing lands on disk.

SKILL.md

≈72 tokens always: the name and description. ≈539 when used: this file. ≈563 more on demand in 1 file.

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. 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)

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides structural guidelines and templates for documenting Oracle-to-PostgreSQL migration bug reports. It does not exhibit any malicious behaviors, execute shell commands, perform network requests, or handle untrusted active inputs.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    2 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at f7e8aaa. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 19 hours ago.

Activeupdated 2 months ago

Topics

README badge

README badge for github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report

What it does

Structures bug reports for Oracle-to-PostgreSQL migration issues, documenting behavioral differences with severity, root cause, and validation steps. Use when migration testing uncovers defects in data handling, type coercion, sequences, or stored procedure compatibility between the two databases.

Generated from the current SKILL.md.

Frequently asked

What Oracle-to-PostgreSQL behavioral differences does this skill document?
The skill creates structured bug reports that capture defects caused by behavioral differences between Oracle and PostgreSQL, such as empty string vs. NULL handling, type coercion strictness, collation, sequence values, time zones, and constraints.
Does this skill provide a bug report template?
Yes. The skill includes a template at references/BUG-REPORT-TEMPLATE.md that mandates Status, Component, Test, Severity, Problem, Scenario, Root Cause, Solution, and Validation sections.
Should I document client code changes in the bug report?
Only if required for correct behavior. The skill guidance is to avoid client code changes when possible; if proposed, they must be documented and justified explicitly in the Solution section.
What severity levels does the bug report format use?
Four levels: Low, Medium, High, and Critical, based on impact scope.
What naming convention should I use for bug report files?
Save reports as BUG_REPORT_<DescriptiveSlug>.md using short PascalCase identifiers (for example, BUG_REPORT_EmptyStringNullHandling.md).

Generated from the current SKILL.md. These answers refresh after source changes.