vegastack

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).

Use VegaStack Pages through its Remote MCP server or standalone vpg CLI for agent-authored documentation review, source editing, anchored comments, templates, publications, workspace trees, review waits, attachments, and safe publish/review workflows. Trigger when an agent needs to create, inspect, edit, validate, comment on, resolve, or template VegaStack Pages documents, or when choosing between MCP tools and the CLI.

Ship workflow for @vegastack/pages. Handles the release cycle: analyze git diff, audit docs for stale references, draft version + CHANGELOG + commit + release notes, then commit, push, tag, and let GitHub Actions publish npm and deploy Cloudflare. TRIGGER: when user runs /ship or asks to ship, release, cut a release, publish, commit and push, or deploy. Only for this project (vegastack-pages).

Release workflow for the notion-markdown-sync plugin. Analyzes changes, drafts changelog entry, bumps version, commits, tags, pushes, and creates a GitHub release. Use when the user says "ship", "release", or "cut a release".

Two-way sync between local markdown files and Notion pages using the Notion Markdown API (v2026-03-11). Use this skill whenever the user wants to: push/upload a local markdown file to create or update a Notion page, pull/download a Notion page to a local markdown file, sync content between local files and Notion (including conflict detection), validate that a markdown file is compatible with Notion's enhanced markdown format (callouts, toggles, tables, colors, etc.), check sync status of tracked files, read/fetch a Notion page's content, batch push multiple markdown files to Notion, fix Notion markdown formatting issues (e.g. converting GitHub-flavored syntax to Notion format), or deal with expired pre-signed file URLs from pulled pages. This skill knows the exact Notion enhanced markdown syntax for all block types and handles YAML frontmatter with sync metadata and database page properties. Do NOT use for: writing Notion SDK/API scripts from scratch, setting up Notion integrations, designing database schemas