# Kalash33 Kstack Ship

> Kalash33 Kstack Ship

- Skill: `tomevault-io/kalash33-kstack-ship` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/kalash33-kstack-ship`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/kalash33-kstack-ship/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/kalash33-kstack-ship

---


# /ship — Release Engineer

Tests pass. Coverage audited. PR opened. Done.

## When to Use

- Code is ready to merge
- After `/review` and `/qa` pass
- When you say "ship it"

## Process

### Step 1: Pre-flight Checks

```bash
# Sync with main
git fetch origin main
git rebase origin/main

# Run tests
{test_command}

# Check for uncommitted changes
git status
```

If tests fail → stop, report, suggest `/qa`.
If merge conflicts → stop, report, help resolve.

### Step 2: Coverage Audit

Run coverage tool and report:
```
Coverage: 87% (target: 80%) ✅
  src/api.ts: 92%
  src/queue.ts: 71% ⚠️ (below target)
  src/utils.ts: 100%
```

### Step 3: Commit & Push

- Ensure all changes are committed with conventional commit messages
- Push to the feature branch
- If no feature branch, create one: `feat/{slug}`

### Step 4: Open PR

Create a PR with:
- **Title**: Conventional format — `feat: {description}` or `fix: {description}`
- **Body**: What changed, why, how to test
- **Labels**: Auto-detect (feature, bugfix, docs, etc.)
- **Linked issues**: If plan references an issue

### Step 5: Report

```
## Ship Report

Branch: feat/notification-triage
Tests: 51 passed, 0 failed
Coverage: 87% (+4% from last ship)
PR: github.com/you/app/pull/42

### Changes
- 3 files changed, +142 -23
- New: src/triage.ts, tests/triage.test.ts
- Modified: src/api.ts
```

## Blockers

Ship will NOT proceed if:
- Tests are failing
- Critical security issues from `/review` are unresolved
- Uncommitted changes exist without explanation
- Branch is behind main with conflicts

## Chaining

- **Before**: `/review` + `/qa` (both should pass first)
- **After**: `/retro` (reflect on what shipped)

---
> Source: [kalash33/kstack](https://github.com/kalash33/kstack) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-15 -->