AGENT SKILL

shipit

Release builds with the shipit CLI. Use when releasing or promoting a build to staging or prod, checking a release manifest, or rolling back a shipit deployment.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 1
Forks
0

01 前言 Front Matter

name
shipit
description
Release builds with the shipit CLI. Use when releasing or promoting a build to staging or prod, checking a release manifest, or rolling back a shipit deployment.

02 资源文件 5

03 SKILL.md 正文

shipit

shipit publishes the current build to a target (staging or prod) and keeps the previous release on each target so it can be rolled back. It reads the version from shipit.yaml in the current directory.

Releasing

  1. Run shipit check before every shipit release. It exits 0 even when the manifest is missing, printing no manifest; treat that as a failure.
  2. Release to staging first, then prod: shipit release --target staging, then shipit release --target prod. Add --dry-run to print the plan without publishing; do so whenever the target is prod.
  3. Release notes use exactly --notes-json '{"items":[{"id":"T-1420","text":"Fix login redirect"}]}'. A bare array, a notes key, or extra keys inside an item are rejected.

Rules

  • Never skip shipit check before a release; a prod release with an invalid manifest once caused a forty-minute outage.
  • shipit purge <release-id> --yes deletes a release's artifacts from the remote store and cannot be undone. Run it only when the human names the release, and pass --yes only after they confirm.
  • Read each command's output before deciding the next command.

Rollback

  1. shipit status shows ACTIVE and PREVIOUS release ids per target.
  2. shipit rollback --target <target>; if it fails, retry with --retries 5.
  3. shipit status again to confirm the previous id is active, then shipit check.
  4. Tell the human which release is now active and which was rolled back, and list the failed release id in the next release's notes.

Global options

--verbose, --quiet (errors only), --no-color, --timeout <seconds> (default 60), --retries <n> (default 2).

04 同仓库更多 Skills

StartupBros-com
StartupBros-com/hov-stack

review-adversarial-first

Operator-invoked adversarial review: 3 refute-by-default lenses plus a deterministic judge against a PR, branch, or path, then a decision on whether /ce-code-review's topic fan-out runs. Off the default merge path since the 2026-10-17 merge-and-end ruling; run only when asked for by name.

★ 1
StartupBros-com
StartupBros-com/hov-stack

memory-mine

Run one deterministic, budgeted directed-capture batch for an explicit Claude Code project store. Use manual workspace mode only when cross-agent cass sessions are intentionally in scope.

★ 1
StartupBros-com
StartupBros-com/hov-stack

papers

Search preprints from arXiv, bioRxiv, and medRxiv without API keys. Supports search, lookup, extraction, citations, enrichment, and paper downloads that bundle PDFs plus linked GitHub code.

★ 1
StartupBros-com
StartupBros-com/hov-stack

papers

Search preprints from arXiv, bioRxiv, and medRxiv without API keys. Supports search, lookup, extraction, citations, enrichment, and paper downloads that bundle PDFs plus linked GitHub code.

★ 1
StartupBros-com
StartupBros-com/hov-stack

wsl-cdp

Drive the user's real, logged-in Windows browser (Chrome, Edge, or Brave) from a Claude Code session running inside WSL2, over the Chrome DevTools Protocol - read authenticated dashboards and consoles, take real screenshots, open and read pages with the user's sessions. Use when a task needs the user's existing web logins and the session runs in WSL2, where the Claude in Chrome extension cannot work. Not for native-Windows or macOS Claude Code (use the official Claude in Chrome extension), not for anonymous scraping or CI (use headless Playwright inside WSL), not for getting past login walls (those are handed to the human).

★ 1
StartupBros-com
StartupBros-com/hov-stack

token-eater

[BETA] Spend a subscription's idle, about-to-expire credits on safe, machine-verified cleanup. You pick the service (Grok / Codex / Claude) and a token-heavy maintenance skill (de-monolithize, de-slop, simplify, dead-code); that service runs the whole skill -> gate -> self-review -> draft-PR loop on its own credits, in an isolated worktree. token-eater verifies the gate and never merges. Manual invocation only during beta.

★ 1