hashgraph-online/awesome-codex-plugins / plugins/ariaxhan/kernel-claude/skills/ship
ship
VerifiedRelease-gate sequence: validate → review → push → tag. Wraps kernel:git mechanics with the pre-ship safety chain. Triggers: ship, release, push to main, ready to merge, deploy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| reference/ship-research.md | markdown | 2.7 KB |
reference/ship-research.md
View on GitHub---
date: 2026-05-28
topic: ship skill — background, rationale, tooling survey
---
# Ship Skill — Reference
## Purpose and mental model
Shipping is not committing. Committing is one step of shipping.
Ship = the full sequence: validate gates → review → push → optionally tag.
Each step has a fail-fast verdict; the chain stops on first failure.
## Skill relationships
- skills/build/reference/git.md — commit mechanics
- skills/quality/SKILL.md — Big 5 self-review checklist
- /kernel:validate — invokes validator agent (full 9-gate safety chain)
- /kernel:review — invokes reviewer agent (>80% confidence threshold)
- agents/pre-ship.md — composite release gate for tier 2+ work (spawns 4 parallel validators)
## Core principles (the "why" behind the sequence)
1. **Validate before review, review before push, push before tag.** The order is fail-fast.
2. **Push to `main` requires explicit user say-so.** Feature branch push is fine after gates pass.
3. **The release is the artifact, not the intent.** Verify by file/diff, not by what you meant to ship.
4. **Tag only when explicitly releasing.** Casual pushes don't get tags.
5. **Hook carve-outs apply to hooks only.** User and agent commits in this skill go through the full gate chain.
## Local gate equivalents (when /kernel:validate unavailable)
Use the project's nearest configured command first (`package.json` scripts, `Makefile`, `pyproject.toml`, `justfile`).
| Gate | Command |
|---|---|
| Tests | `npm test` / `pytest` / `cargo test` |
| Types | `tsc --noEmit` / `mypy` / `cargo check` |
| Lint | `eslint` / `ruff` / `cargo clippy` |
| Security | `npm audit` / `pip-audit` / project scanner |
| Diff sanity | `git diff --stat {main}..HEAD` — no unrelated changes, no leaked secrets |
## Tag format details
- Semver projects: read version from manifest (`package.json`, `Cargo.toml`, `pyproject.toml`), confirm next version with user.
- Command: `git tag -a v{X.Y.Z} -m "{release notes summary}"` then `git push origin v{X.Y.Z}`.
- Non-versioned projects: timestamp tag if requested, otherwise skip.
- Check before tagging: `git tag -l` to avoid overwriting existing tags.
## Profile-gated post-ship actions
- `github-oss` / `github-production`: post PR or release note via `gh` CLI / GitHub integration hooks.
- `local`: nothing further beyond agentdb checkpoint.
## Why the ask_user gates exist
Three mandatory pause points prevent autonomy overreach:
1. **Preflight ambiguity** — wrong branch or unexpected commit range is a pre-condition failure, not a recoverable error.
2. **Review COMMENT (not REQUEST CHANGES)** — comments are advisory; the human decides if they block.
3. **Push to main** — NEXUS I0.8 is non-negotiable; explicit confirmation is the external hook equivalent for this gate.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |