메뉴
Use when the user asks to send/announce release info or release notes for the terraform-provider-cato to Slack. It posts a release announcement to
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create or update mock data for Terraform provider acceptance tests using recorded GraphQL calls under tmp_recorded and replay fixtures under test_data. Use when Codex needs to generate or refresh mocked API data for acctests instead of real Cato API calls, inspect GraphQL operationName traffic, build accmock config.yaml files, or create resource mock YAML files for TF_ACC_MOCK=1 runs.
Write high-coverage Go unit tests for terraform-provider-cato resources, data sources, validators, plan modifiers, hydrators, and API payload translation. Use when agent is asked to add or update tests in this repository, especially for modified files under internal/provider, when SDK/API calls need mockery-generated interfaces, or when validating Terraform Plugin Framework Create/Read/Update/Delete/Import behavior without real Cato API calls.
Use when the user asks to prepare the release of a new version of the terraform provider living in this repository. It will create a new release branch, update the version in the appropriate files, and create a changelog entry with the changes since the last release.
Use when the user asks to publish the release of a new prepared version of the terraform provider living in this repository. It will create a new release in the repository with the appropriate tag and release notes based on the changelog entry created during the prepare-release step.
| name | send-release-info |
| description | Use when the user asks to send/announce release info or release notes for the terraform-provider-cato to Slack. It posts a release announcement to |
Before using this skill:
terraform-provider-cato repository.Announce a released version of the terraform provider on Slack. This skill:
#rn-kb-opensource-api-announcements.#management-integrations.This skill only communicates a release that already exists. It does not bump
versions, edit the changelog, tag, or publish — use prepare-release and
publish-release for those steps.
#rn-kb-opensource-api-announcements — channel ID C08QPHRURP1.#management-integrations — channel ID C0A7P8V7WFR.Before drafting the message, gather the release facts from the repository, not from memory:
changelog.md. If the user names a version, use that one and confirm it
exists in changelog.md.changelog.md entry to get the release date (the
## X.Y.Z (YYYY-MM-DD) header) and the list of changes.Added and
user-facing Fixed/Changed items; omit purely internal Tests/chore
items unless nothing else is notable).Match the format of the existing announcements, e.g.
https://canu.slack.com/archives/C08QPHRURP1/p1782466704793209.
Use this template (Slack markdown: italic title, code for version/date,
bulleted highlights, and named links):
_Terraform Provider Cato `vX.Y.Z` is available_
Released: `YYYY-MM-DD`
Highlights:
- <highlight 1>
- <highlight 2>
Links:
- [Provider registry](https://registry.terraform.io/providers/catonetworks/cato/latest)
- [Changelog](https://github.com/catonetworks/terraform-provider-cato/blob/main/changelog.md)
Notes:
v (e.g. v0.0.90).Follow this order:
slack_send_message_draft for
#rn-kb-opensource-api-announcements (C08QPHRURP1) and get confirmation.#rn-kb-opensource-api-announcements with
slack_send_message and capture the returned message permalink.#management-integrations (C0A7P8V7WFR) a short message linking to the announcement, e.g.
Terraform Provider Cato vX.Y.Z released — announcement: <permalink>.Always:
changelog.md, not assumptions.#management-integrations message.Never:
#management-integrations before the announcement has been posted (the internal
message must link to the real announcement).User request that should trigger this skill:
Send the release info for the latest terraform provider version to Slack.