If you're migrating from Oracle to Postgres and hitting behavioral differences, this gives you a structured template for documenting them as proper bug reports. It enforces the format: status, severity, reproduction steps, root cause, and validation. The guidance treats Oracle as the source of truth and calls out the usual suspects like empty string vs NULL, type coercion, and collation differences. Honestly, the real value is keeping your team from writing vague bug reports that say "it works in Oracle but not Postgres" without the details anyone needs to actually fix it. Saves as BUG_REPORT_DescriptiveSlug.md and includes a reference template.
npx -y skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
cursor/plugins
github/awesome-copilot
alirezarezvani/claude-skills
microsoft/win-dev-skills