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.0 KB
- 参考文档status.txt62 B
- 参考文档tools.txt503 B
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 shipit.yaml in the current directory, so run it from the project root.
Rules
- Run
shipit checkbefore everyshipit release; never skip it. (A prod release once went out with an invalid manifest and caused a 40-minute outage.) shipit checkexits 0 even when the manifest is missing; it printsno manifeston stderr. Treat that as a failure, not a pass.shipit purge <release-id> --yespermanently deletes a release's artifacts from the remote store. Run it only when the human names the release to purge, and pass--yesonly after they confirm.- Read each command's output before deciding the next command.
Releasing
shipit check- Dry run first, always for prod:
shipit release --target prod --dry-runprints the plan and publishes nothing. - Release to staging, then to prod:
shipit release --target staging, thenshipit release --target prod.
The flag is --target, not --env.
Release notes are optional JSON, in exactly this shape (a bare array, a notes key, or extra keys inside an item are rejected):
shipit release --target prod --notes-json '{"items":[{"id":"T-1420","text":"Fix login redirect"}]}'
Rollback
If a release fails:
shipit statusshows ACTIVE and PREVIOUS release ids per target.shipit rollback --target <staging|prod>shipit statusagain; confirm the 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 itself fails, rerun it with
--retries 5. - Include the failed release id in the notes of the next release.
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 runs ignore --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.