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-02
- Stars
- ★ 0
- 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 资源文件 4
- 参考文档init.json2.2 KB
- 参考文档reply.txt1.2 KB
- 参考文档status.txt62 B
- 参考文档tools.txt479 B
03 SKILL.md 正文
shipit
shipit publishes the current build to a target (staging or prod) and keeps the previous release on each target for rollback. It reads shipit.yaml in the current directory. Run shipit <command> --help for exact flags.
Releasing
- Run
shipit check. A pass prints nono manifestline.shipit checkexits 0 even when the manifest is missing, printingno manifeston stderr, so read the output and treat that line as a failure; stop and tell the human. - Preview with
shipit release --target <target> --dry-run. Always do this for prod. - Release to staging, then to prod:
shipit release --target staging, thenshipit release --target prod. The flag is--target;--envdoes not exist. - Run
shipit statusand confirm the new release id is ACTIVE on that target.
Check before every release, because an unvalidated manifest once took prod down.
Release notes
Pass notes with --notes-json, in exactly this shape:
shipit release --target prod --notes-json '{"items":[{"id":"T-1420","text":"Fix login redirect"}]}'
A bare array, a notes key, or extra keys inside an item are rejected.
Rollback
shipit statusshows ACTIVE and PREVIOUS release ids per target.shipit rollback --target <target>returns that target to its PREVIOUS release.shipit statusagain; confirm the old PREVIOUS id is now ACTIVE.shipit checkto confirm the manifest still validates.- Tell the human which release is now active and which was rolled back.
- If the rollback fails, rerun it with
--retries 5. - Put the failed release id in the notes of the next release.
Purge
shipit purge <release-id> --yes deletes a release's artifacts from the remote store and cannot be undone. Run it only for a release the human names, and add --yes only after they confirm.
Global options
--verbose Print each step as it runs
--quiet Print only errors
--no-color Disable colored output
--timeout <seconds> Give up on a remote call after this long (default 60)
--retries <n> Retry failed remote calls this many times (default 2)
--dry-run ignores --retries.
04 同仓库更多 Skills
tune
Find and fix real defects in a skill, AGENTS.md, or CLAUDE.md, then prove the description still routes. Runs the bundled token-spending runner, so it starts only on the human's explicit instruction.
skill-tuner
Evidence-tagged rules for writing documents agents consume. Use when creating, editing, or shortening skills, AGENTS.md, or CLAUDE.md.
portfolio
Inventory every skill the agent is shown, with its per-turn listing cost, usage count and visibility knob, then decide one skill at a time whether the model should start it on its own. Reads files only; starts on the human's explicit instruction.
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.
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.
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.