本文へ移動
cccskills
無料GitHub で公開

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

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.4 KB
  • references/BUG-REPORT-TEMPLATE.md2.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

日本語の概要は準備中です。原文の説明を表示しています。

github/awesome-copilot4万2026年10月9日 更新

Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.

日本語の概要は準備中です。原文の説明を表示しています。

github/awesome-copilot4万2026年10月9日 更新

Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.

日本語の概要は準備中です。原文の説明を表示しています。

github/awesome-copilot4万2026年10月9日 更新

Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.

日本語の概要は準備中です。原文の説明を表示しています。

github/awesome-copilot4万2026年10月9日 更新

Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.

日本語の概要は準備中です。原文の説明を表示しています。

github/awesome-copilot4万2026年10月9日 更新

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

日本語の概要は準備中です。原文の説明を表示しています。

github/awesome-copilot4万2026年10月9日 更新

github のスキルをすべて見る

このスキルの問題を報告する