菜单
Prepare beta-line or stable release PRs for terraform-provider-ona by selecting the next provider version, updating version/STABLE_VERSION, version/BETA_VERSION, and CHANGELOG.md as appropriate, validating release metadata, and describing the publish step.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Safely create, edit, review, import, plan, and troubleshoot Terraform configurations using the gitpod-io/ona provider and ona_* resources. Use for Ona provider setup, resources, data sources, ephemeral resources, Terraform Query, imports, state safety, and provider diagnostics. Do not use for developing the provider's Go implementation.
Build, extend, review, test, or debug the Ona Terraform provider in Go with the Terraform Plugin Framework. Use for provider resources, data sources, ephemeral resources, schema/model changes, import behavior, state drift, generated docs/examples, local Terraform dev loops, acceptance tests, or questions like adding a resource, fixing a perpetual diff, or keeping tokens out of state.
Go test patterns for this Terraform provider using table-driven tests, the Expectation pattern, and cmp.Diff. MUST be consulted before writing Go test code, including tests added as part of a larger feature implementation. Use when writing, adding, or fixing Go tests; working with _test.go files; implementing Go behavior that needs test coverage; adding unit tests; testing Terraform provider mapping/model/diagnostic behavior; adding acceptance tests with Terraform Plugin Testing; or verifying Go code with tests. Triggers on "Go test", "write tests", "add tests", "test coverage", "unit test", "_test.go", "verify with tests", "test the implementation", "add test cases", "table-driven test", "cmp.Diff", or any Go implementation task that includes a testing step.
Create a pull request for changes in terraform-provider-ona. Use when asked to create a PR, open a PR, submit changes, land changes, prepare a branch, commit changes, write a PR description, or summarize verification.
Review code changes in this Terraform provider repository. Use when asked to review, self-review, check a diff, review a PR, or assess changes to Go provider code, Terraform docs, examples, generation, release scripts, or CI for terraform-provider-ona.
Write, edit, or review Terraform provider documentation and examples for terraform-provider-ona. Use for README updates, generated provider docs, examples, release docs, local dev-loop docs, import workflows, and developer-facing prose.
| name | release-prep |
| description | Prepare beta-line or stable release PRs for terraform-provider-ona by selecting the next provider version, updating version/STABLE_VERSION, version/BETA_VERSION, and CHANGELOG.md as appropriate, validating release metadata, and describing the publish step. |
Use this skill when asked to prepare, review, or reason about an Ona Terraform provider release PR.
version/STABLE_VERSION is the reviewed stable release intent and contains exact bare SemVer, for example 0.2.0.version/BETA_VERSION is the reviewed beta release line and contains a bare beta line without the numeric suffix, for example 0.3.0-beta.v, for example v0.2.0 or v0.3.0-beta.7.terraform-registry-manifest.json version is the Registry manifest schema version, not the provider version.main run CI and automatically publish the next beta tag from version/BETA_VERSION.Build main workflow run from main with release_channel=stable after the stable release-prep PR merges.main.version/BETA_VERSION to the intended beta line, for example 0.3.0-beta.version/STABLE_VERSION to exact bare SemVer and update the first CHANGELOG.md heading to the same version.scripts/validate-release-version.sh --channel stablescripts/validate-release-version.sh --channel betamain publishes the next computed v...-beta.N tag.Build main workflow manually from main with release_channel=stable.main.v in version/STABLE_VERSION or version/BETA_VERSION.version/BETA_VERSION; tags carry the auto-incrementing .N suffix.