gitpod-io

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.

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.

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.

Create, update, and sync Ona automations. Ensures YAML files in .ona/automations/ stay in sync with the live Ona automation registry. Use when creating a new automation, modifying triggers or prompts, deleting an automation, or auditing drift between YAML and live state. Triggers on "create automation", "update automation", "delete automation", "sync automations", "register automation", "automation drift", "add a new automation", "change automation triggers".

Triage unlabeled GitHub Issues, decompose product specs into backlog items, and ensure issue quality for the automation loop. Reads the product spec, triages user-created issues, creates issues with acceptance criteria and dependency chains, and sets up labels for the autonomous Feature Builder. Use when starting a new product, adding a new feature area, re-planning after a scope change, or triaging incoming feature requests and bug reports. Triggers on "plan features", "create backlog", "decompose spec", "what should we build", "create issues", "plan the product", "triage issues", "review backlog".

Documents how feature requests and bug fixes flow through the automation system. Use when asked about the development process, how to submit a feature request, how bugs get fixed, or how the automations work together. Triggers on "how do I submit a feature", "how do bugs get fixed", "development process", "automation workflow", "how does the backlog work", "how are issues handled", "what automations exist".

Scan, triage, and remediate CVEs in the Gitpod monorepo. Use when asked to fix vulnerabilities, update dependencies for security, respond to CVE scan failures, or validate that dependency updates resolve known CVEs. Triggers on "fix CVE", "vulnerability scan", "security update", "dependency CVE", "grype scan", "leeway sbom", "CVE remediation", "update vulnerable dependency", "daily scan failure", "critical vulnerability".