What problem does it solve?
Contributing a new capability to the gcx CLI requires deciding where a command belongs (provider, datasource, resource adapter, cloud command, or skill), designing its agent-facing contract, and catching recurring review defects before a human reviews the PR. This Skill walks a contributor and their coding agent through that entire process inside a grafana/gcx checkout.
Core Features & Use Cases
- Placement decisions: Determines whether a capability needs a new command, an extension of an existing one, or no gcx surface at all, with a backend-readiness gate that names owners for missing prerequisites.
- Contract design: Covers naming, typed inputs, output protocol class, completeness disclosure, error vocabulary, and token cost so agents can route on the command metadata.
- Diff-triggered self-review: Runs targeted checks (T1-T12) for defect classes like dead codec paths, empty-flag handling, truncation disclosure, and fix-push regressions.
- Use Case: You want to expose your Grafana product's API through gcx. The Skill inventories the command tree, probes the backend, drafts the command contract, hands off to add-provider or add-datasource skills, and reviews the resulting diff before the PR.
Quick Start
Ask your coding agent to integrate your product's API with gcx by adding a new command, starting from a grafana/gcx repository checkout.