메뉴
Use when creating a PR for a non-trivial bug fix in this repo. Assembles a structured PR description following .github/PULL_REQUEST_TEMPLATE.md with expanded sections for root cause, risks, and test plan. Do NOT use for trivial one-liner fixes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when a Terraform Plugin Framework resource import reads required DynamicAttribute values. Handle imported partial state before converting dynamic values.
Use when changing coralogix_data_enrichments update semantics or drift tests. Prefer state-ID delete plus add over partial atomic overwrite for scoped replaces.
Use when validating a Coralogix terraform-provider bug fix end-to-end against a real Coralogix environment. Builds the provider locally, runs multi-step Terraform apply/plan scenarios to verify idempotency, and catches perpetual-diff regressions before merge.
SOC 직업 분류 기준
| name | create-pr |
| description | Use when creating a PR for a non-trivial bug fix in this repo. Assembles a structured PR description following .github/PULL_REQUEST_TEMPLATE.md with expanded sections for root cause, risks, and test plan. Do NOT use for trivial one-liner fixes. |
Trigger: opening a PR for a non-trivial bug fix. Trivial one-liners can keep the default template body as-is.
Use .github/PULL_REQUEST_TEMPLATE.md as the skeleton — keep every section (Description, Acceptance tests, Release Note, References, Community Note). Don't drop the Community Note or other boilerplate.
Inside the Description section, use these ## headers in order:
file:function refs if compounding.git log --follow / git blame. If unclear, say so; don't speculate from commit-message phrasing.| File | Change | table.Fill the rest of the template: answer the Acceptance tests checkboxes, paste relevant make testacc TESTARGS='-run=...' output, write a meaningful Release Note (NONE for chore/internal), link related PRs/issues in References, keep Community Note verbatim.
Before gh pr create: show the assembled description and wait for explicit approval. PR creation is visible-to-others.
Why: reviewers shouldn't redo the archaeology you did. Symptom-and-fix descriptions push the work back onto them.