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.3 KB
- 参考文档reply.txt1019 B
- 参考文档status.txt62 B
- 参考文档tools.txt738 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. shipit checkexits 0 even when the manifest is missing, and printsno manifeston stderr. Treat that line as a failure: do not release.- Release to staging first, then prod.
- Dry-run (
--dry-run) every prod release first, and read the plan before the real run. shipit purge <release-id> --yesdeletes a release's artifacts from the remote store and cannot be undone. Run it only when the human names the release to purge, and add--yesonly after they confirm.- Read each command's output before deciding the next command.
Releasing
shipit checkshipit release --target stagingshipit release --target prod --dry-run, thenshipit release --target prod
The flag is --target; --env is not accepted.
Release notes are JSON passed with --notes-json:
shipit release --target prod --notes-json '{"items":[{"id":"T-1420","text":"Fix login redirect"}]}'
The shape is exactly {"items":[{"id":"...","text":"..."}]}. A bare array, a notes key, or extra keys in an item are rejected (exit 2).
Rollback
If a release fails:
shipit statusto see the active and previous release on each target; note the previous release id.shipit rollback --target <staging|prod>shipit statusagain and confirm the previous id is now active.shipit checkto confirm the manifest still validates.- If the rollback itself fails, rerun with
--retries 5. - Tell the human which release is now active and which was rolled back, and put 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)
Background
In March 2026 a release went to prod with a manifest that failed validation and caused a forty-minute outage because nobody ran the check. Older docs may mention make deploy; the team moved to shipit from a Makefile in January.
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.