VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:ship

Unified Ship Pipeline

Takes a completed feature branch through target detection, issue linking, merge, tests, review, versioning, changelog, journal/docs, commit, push, PR creation, optional reviewed merge, and opt-in social publishing.

01

Pre-flight and mode

02

Link issues

03

Merge target

04

Run tests

Rule 01

Auto-detect project conventions instead of asking early

Rule 02

Never skip tests unless the user passed --skip-tests

Rule 03

Regular push only; never force-push or bypass branch protection

Rule 04

Prefer honest Not run/Unavailable evidence over invented PR narrative

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Pre-flight and mode Check the branch, normalize official/stable/main or beta/dev/next, let --both supersede mode tokens, inspect status/diff, and include uncommitted work.
  2. 2 Link issues Find or create related GitHub issues in one batch, then carry the linked issues into the structured PR body.
  3. 3 Merge target Fetch and merge origin/<target-branch>; stop with conflicts instead of hiding or force-resolving unrelated work.
02

Work

Agent / skill execution

  1. 4 Run tests Auto-detect the test runner, delegate execution, and stop on failures unless the user explicitly passed --skip-tests.
  2. 5 Review Run the two-pass pre-landing review, treating critical issues as blockers while informational findings remain evidence.
  3. 6 Version and changelog Auto-detect version and changelog files, bump patch automatically, ask on major/minor bumps, and silently skip missing files.
03

Verify

Gate, review, validation

  1. 7 Journal, docs, plan Run journal and official-mode docs updates in the background unless skipped, and finalize/link a plan when the ship is plan-backed.
  2. 8 Commit, push, PR Create the conventional commit, push the current branch normally, and create a PR with honest evidence, linked issues, and ship mode.
  3. 9 Optional merge/social If --merge is present, hand the PR to ak:review-pr --fix --reply --merge; if --social is present, publish only after green gates and required opt-ins.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:ship [official|stable|main|beta|dev|next] [--both] [--advice] [--merge] [--skip-tests] [--skip-review] [--skip-journal] [--skip-docs] [--social] [--yes-post] [--yes-post-private] [--dry-run]

Arguments

[official|stable|main|beta|dev|next]

Release mode

Optional mode token. official, stable, and main normalize to the official path and target the detected default branch; beta, dev, and next normalize to the beta path and target the detected development branch. Omit it only when branch naming can safely choose the mode.

/ak:ship official

Shared options

--both

Ship both targets

Runs the beta stage first, then a gated stable stage. It supersedes any positional mode token and never bypasses branch protection.

/ak:ship --both --merge
--advice

Ask Kongming

Adds advisory-only Kongming checkpoints to the local ship-to-PR path. Advice cannot replace tests, review, or ownership by the main agent.

/ak:ship beta --advice
--merge

Reviewed merge

After PR creation, delegates to ak:review-pr with fix, reply, merge, and post-merge CI convergence. Without this flag, ak:ship does not merge the PR.

/ak:ship official --merge
--skip-tests

Skip tests

Omits the test gate only when equivalent evidence already exists; the PR must record that skip evidence honestly.

/ak:ship --skip-tests
--skip-review

Skip local review

Omits the pre-landing review step. It does not approve the PR and does not skip the downstream ak:review-pr path requested by --merge.

/ak:ship --skip-review
--skip-journal

Skip journal and social

Omits the background technical journal and suppresses the entire social step; code and PR evidence gates still apply.

/ak:ship --skip-journal
--skip-docs

Skip docs update

Omits the official-mode docs update. Beta mode skips that docs step automatically.

/ak:ship official --skip-docs
--social

Social draft

After the required green PR gate, composes build-in-public posts from PR, issue, and plan context. Without --yes-post, it renders only and makes no API call.

/ak:ship --social
--yes-post

Publish social

Allows --social to publish instead of rendering only. It has no publishing effect without --social.

/ak:ship --social --yes-post
--yes-post-private

Private post opt-in

Second explicit opt-in required before publishing social posts about a private repository. It requires --social and --yes-post.

/ak:ship --social --yes-post --yes-post-private
--dry-run

Preview only

Reads pre-flight state and prints the proposed pipeline without delegation, review-merge, social publishing, mutation, or stable-stage simulation for --both.

/ak:ship --dry-run

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Auto-detect ship Recommended 
/ak:ship
Use when:
A completed branch needs the standard PR shipping workflow.
Expected:
Runs pre-flight mode detection, issue linking, target merge, tests, review, version/changelog updates, commit, push, and PR creation, then returns the PR URL or exact blocker.
Beta supervised merge 
/ak:ship beta --advice --merge
Use when:
A completed branch should ship toward a development branch with Kongming advice and reviewed landing.
Expected:
Normalizes beta mode, runs required advisory checkpoints during the local ship-to-PR path, creates the PR, then delegates reviewed merge and CI convergence to ak:review-pr.
Dual target 
/ak:ship --both --merge
Use when:
A completed change needs beta first and a gated stable promotion after green beta.
Expected:
Runs the beta stage first, requires the stable-stage gate before promotion, delegates requested reviewed merge, and stops if the promotion would sweep unrelated work.
Social dry run 
/ak:ship official --social
Use when:
A completed official-mode ship should also render build-in-public copy after PR creation.
Expected:
Creates the ship PR, composes a journal-backed build-in-public draft from PR/issue/plan context, and prints channel posts without calling publishing APIs unless --yes-post is also present.

Handled Scope

  • PR shipping
  • mode detection
  • release notes
  • reviewed merge
  • build-in-public publishing

Next