From greenlight
Ship a change through Greenlight's loop — deploy to preview/beta, verify with the shared harness, then gated-promote develop→main to prod. Use when making a change to a Greenlight tool or the blog and you want it shipped with confidence, or when explicitly asked to deploy/verify/promote.
How this skill is triggered — by the user, by Claude, or both
Slash command
/greenlight:deploy-verify-promoteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The execution discipline for changing a Greenlight tool or the blog. The verify
The execution discipline for changing a Greenlight tool or the blog. The verify harness and promote guard are the same code CI runs, so passing locally means passing in CI. This is what lets a change (or a long string of changes) be shipped with objective confidence rather than vibes.
<name> — a manifest entry: blog, or a tool name from greenlight.config.ts.| Subject | prod | beta |
|---|---|---|
| tool | https://<name>.<domain> | https://beta.<name>.<domain> |
| blog (apex) | https://<domain> | https://beta.<domain> |
| mcp connect | (tool url) + /mcp | same + /mcp |
preview is per-target and comes from the adapter's deploy() result. Everything
else is computed by resolveUrl in @rtrentjones/greenlight-shared.
git checkout -b <type>/<slug> (e.g. post/hello, fix/mcp-auth).runLoop (build → deploy → verify) from @rtrentjones/greenlight-loop.pnpm greenlight verify <name> --url <preview-or-localhost-url>.develop → beta deploy. pnpm greenlight verify <name> --env beta.
Mode is chosen by lane: api/playwright for web, mcp for MCP servers.pnpm greenlight promote <name>. Checks the fast-forward guard
(develop → main). If it refuses (diverged main), reconcile and retry — never force-push.pnpm greenlight verify <name> --env prod.verify exits non-zero if any check fails; the report lists each. Never promote a
tool whose beta verify is failing./mcp; verify handles this by lane.In standalone repos (BAMCP, ejected tools) this skill is delivered by the Greenlight
Claude Code plugin (Phase 7), and the mechanics by the @rtrentjones/greenlight* npm
deps; the per-repo parameters come from that repo's greenlight.config.ts.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub rtrentjones/greenlight --plugin greenlight