Guide · Agent skill
How to use the Oracle-to-PostgreSQL Bug Reports agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
This guide explains how to install and use the creating-oracle-to-postgres-migration-bug-report agent skill, which tells an AI agent to write defect reports in a fixed format when an Oracle database application behaves differently on PostgreSQL. It is for engineers and migration leads who want every bug write-up to look the same. By the end you will know how to install the skill, how to ask for a report with a natural request, and what the finished report contains.
Oracle-to-PostgreSQL Bug Reportsgithub/awesome-copilot · MIT Download the skill Quick start
- 1Download the skill. Download the ZIP of the creating-oracle-to-postgres-migration-bug-report skill from this page.
- 2Unzip it into the right folder. Unzip into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder to limit it to that project.
- 3Or upload it in the Claude apps. In the Claude apps, go to Settings, then Capabilities, then Skills, and upload the skill.
- 4Describe the defect. Explain the Oracle vs PostgreSQL difference in plain language, including the component and seed data.
- 5Review the report. Check the status, severity, reproduction steps, root cause and validation steps against the template.
- 6Save to the standard path. Save the report under .github/oracle-to-postgres-migration/Reports/{ProjectName}/ using the BUG_REPORT_<DescriptiveSlug>.md pattern.
What is an agent skill and what does this one do?
An agent skill is a folder containing a SKILL.md file and optional reference files. When installed, the agent reads the skill when your request matches its description, and then follows its instructions. This skill is named creating-oracle-to-postgres-migration-bug-report and is described as creating structured bug reports for defects found during Oracle-to-PostgreSQL migration.
Once active, the agent documents a behavioral difference between Oracle and PostgreSQL in a fixed template. Each report covers status, affected component, related tests, severity, expected Oracle behavior versus observed PostgreSQL behavior, step-by-step reproduction, root cause, proposed fix with file paths, and how to validate the fix on both databases. Reports are saved to a standard folder and filename pattern.
How do you install the skill?
You have two options. For a personal setup, download the ZIP of the skill from this page and unzip it into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder instead.
If you use the Claude apps, you can upload the skill instead. Go to Settings, then Capabilities, then Skills, and upload the skill there.
- Personal: unzip into ~/.claude/skills/
- Single project: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills
How do you trigger the skill with a natural request?
You do not need a special command. Describe the defect in plain language and mention that it is a migration bug or a difference between Oracle and PostgreSQL. The skill's description covers documenting behavioral differences as actionable bug reports with severity, root cause and remediation steps, so requests phrased around those ideas are the best match.
- Write a bug report for the empty string vs NULL difference we found in the customer repository.
- Document this Oracle vs PostgreSQL behavior as a bug report with severity and root cause.
- Review this migration bug report from a developer and check it has all the required sections.
What does a finished report look like?
Each report follows the template in references/BUG-REPORT-TEMPLATE.md. The header holds the status, which is RESOLVED, UNRESOLVED or IN PROGRESS, plus the component, related test names and severity (Low, Medium, High or Critical). The body then gives the problem, the scenario, the root cause and the solution.
The skill asks for ordered reproduction steps with seed data, the operation, the expected Oracle result and the actual PostgreSQL result. It also asks for minimal SQL excerpts and to omit sensitive data. Oracle is treated as the source of truth for expected behavior.
- Data layer nuances to call out: empty string vs NULL, type coercion strictness, collation, sequence values, time zones, padding and constraints
- Client code changes should be avoided unless needed for correct behavior, and must be justified when proposed
- Reports are saved as .github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md
What does the skill need and what does it run?
The skill lists no required tools or dependencies. It does not run scripts and does not use the network. It consists of SKILL.md and references/BUG-REPORT-TEMPLATE.md, which are read as instructions and templates.
Because it only shapes how the agent writes reports, review what it produces before you commit reports to a repository, since the agent may propose changes based on your code.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
What tips help the reports stay useful?
Give the agent concrete facts: the component name, the seed data you used, and the exact Oracle and PostgreSQL results you observed. The template asks for these, so the more you supply, the fewer gaps the agent has to fill. Keep the slug descriptive so the filename explains the defect at a glance.
- Name the component, such as an endpoint, repository or stored procedure
- Provide the seed data and the exact operation
- Use a PascalCase slug such as EmptyStringNullHandling
- Ask for validation steps that run on both databases
What people use it for
- Recording an empty string stored in Oracle that comes back as NULL on PostgreSQL, with seed data and a reproduction scenario
- Writing a bug report for a RefCursor unwrapping failure in a data access layer, with severity and a proposed fix file path
- Reviewing reports from several developers so they all use the same status, severity and validation format
- Documenting a type coercion difference that makes a query fail on PostgreSQL but succeed on Oracle
Frequently asked questions
How do I install the Oracle to PostgreSQL bug report skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps you can instead upload it under Settings, then Capabilities, then Skills.
Does this skill require anything else to run?
The skill lists no required dependencies. It runs no scripts and uses no network access. It only provides instructions and a report template.
Is the skill free to use?
The skill is published under the MIT licence. Check the licence file in the source repository for the full terms.
Can it help with query tuning or schema migration?
No. The skill only covers writing bug reports for Oracle-to-PostgreSQL behavioral differences. It does not tune queries or migrate schemas.
Where does the agent save the reports?
Reports are saved to .github/oracle-to-postgres-migration/Reports/{ProjectName}/BUG_REPORT_<DescriptiveSlug>.md, where ProjectName is the assembly or folder name with spaces replaced by hyphens.
What if the agent does not pick up the skill?
Confirm the folder is in ~/.claude/skills/ or the project's .claude/skills/ and that SKILL.md is inside it. Then phrase your request around documenting an Oracle vs PostgreSQL difference as a bug report, since that matches the skill's description.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits engineers and migration leads who need consistent, structured defect reports for an Oracle-to-PostgreSQL migration, with Oracle treated as the baseline. It is not useful for general PostgreSQL or Oracle administration, query tuning, schema migration, or projects that are not doing a migration.
Download the skill