vegastack-cli

Ship workflow for the @vegastack/cli npm package — INTERNAL v0.1 GitHub Packages release path, ONLY for the vegastack-cli repo. Handles the full release cycle: pre-flight tests across CLI + apps/mcp + apps/dashboard, diff analysis, exhaustive doc audit, version bump synced across 3 package.json files, changelog entry in Keep a Changelog format, conventional commit, push, tag, GH Packages publish via publish-internal.yml, post-ship verification. TRIGGER: when the user runs /ship, says 'cut a release', 'ship the cli', 'publish to internal registry', 'release v0.1.1', or anything that means ship a new version of @vegastack/cli from inside this repo. Make sure to use this skill whenever the user wants to ship a release of @vegastack/cli, even if they don't explicitly say 'ship' — phrases like 'let's release this', 'tag v0.1.x', 'publish a new version', or 'cut a build' should all trigger it. Do NOT trigger for other projects (mac-dev-env-setup has its own /ship), for the bundle repo (engg-vegastack-agent-tf-provi

Use when the user asks to write, debug, import, or migrate Terraform / HCL, or names any cloud / SaaS provider in a "deploy / provision / configure" context. Provides per-resource argument schemas, import-ID formats, deprecation flags, recent-change knowledge cards, cross-provider recipes, and recommended-companion expansion — all from a local doc bundle, no network calls. Triggers on "create a <resource>", "import <resource>", "what arguments does X accept", "is <resource> deprecated", "set up <multi-service stack>", and `*.tf`/`*.hcl` file edits. Do NOT use for: pure shell / bash / Python questions; non-IaC cloud questions ("what's the cheapest EC2 size?"); CDK / Pulumi / Crossplane (different DSLs); Terraform Cloud workspace administration (separate API).

Use when the user asks to write, debug, import, or migrate Terraform / HCL, or names any cloud / SaaS provider in a "deploy / provision / configure" context. Provides per-resource argument schemas, import-ID formats, deprecation flags, recent-change knowledge cards, cross-provider recipes, and recommended-companion expansion — all from a local doc bundle, no network calls. Triggers on "create a <resource>", "import <resource>", "what arguments does X accept", "is <resource> deprecated", "set up <multi-service stack>", and `*.tf`/`*.hcl` file edits. Do NOT use for: pure shell / bash / Python questions; non-IaC cloud questions ("what's the cheapest EC2 size?"); CDK / Pulumi / Crossplane (different DSLs); Terraform Cloud workspace administration (separate API).