creating-oracle-to-postgres-migration-bug-report
installsforks
How to install creating-oracle-to-postgres-migration-bug-report?
github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report
$npx -y skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-reportCreates 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.
SKILL.md
| 1 | # Creating Bug Reports for Oracle-to-PostgreSQL Migration |
| 2 | |
| 3 | ## When to Use |
| 4 | |
| 5 | - Documenting a defect caused by behavioral differences between Oracle and PostgreSQL |
| 6 | - Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project |
| 7 | |
| 8 | ## Bug Report Format |
| 9 | |
| 10 | Use the template in [references/BUG-REPORT-TEMPLATE.md](references/BUG-REPORT-TEMPLATE.md). Each report must include: |
| 11 | |
| 12 | - **Status**: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS |
| 13 | - **Component**: Affected endpoint, repository, or stored procedure |
| 14 | - **Test**: Related automated test names |
| 15 | - **Severity**: Low / Medium / High / Critical — based on impact scope |
| 16 | - **Problem**: Expected Oracle behavior vs. observed PostgreSQL behavior |
| 17 | - **Scenario**: Ordered reproduction steps with seed data, operation, expected result, and actual result |
| 18 | - **Root Cause**: The specific Oracle/PostgreSQL behavioral difference causing the defect |
| 19 | - **Solution**: Changes made or required, with explicit file paths |
| 20 | - **Validation**: Steps to confirm the fix on both databases |
| 21 | |
| 22 | ## Oracle-to-PostgreSQL Guidance |
| 23 | |
| 24 | - **Oracle is the source of truth** — frame expected behavior from the Oracle baseline |
| 25 | - Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints |
| 26 | - Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly |
| 27 | |
| 28 | ## Writing Style |
| 29 | |
| 30 | - Plain language, short sentences, clear next actions |
| 31 | - Present or past tense consistently |
| 32 | - Bullets and numbered lists for steps and validations |
| 33 | - Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible |
| 34 | - Stick to existing runtime/language versions; avoid speculative fixes |
| 35 | |
| 36 | ## Filename Convention |
| 37 | |
| 38 | Save bug reports as `BUG_REPORT_<DescriptiveSlug>.md` where `<DescriptiveSlug>` is a short PascalCase identifier (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`). |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
