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:vibe

Autonomous development pipeline

Run the full autonomous development pipeline from issue or feature request through worktree, plan, implementation, review, PR, ready labels, and optional merge/CI convergence.

01

Parse request

02

Create worktree

03

Plan gates

04

Sync issue

Rule 01

One command owns the pipeline, but each underlying skill keeps its own gates.

Rule 02

GitHub issues are source of truth; do not duplicate an existing issue.

Rule 03

Work happens in an isolated worktree, never directly on protected base branches.

Rule 04

Bugfix routes go through ak:fix; feature routes go through ak:cook.

Rule 05

Ready labels mean reviewed, fixed, replied, and CI/accountable blockers handled.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Parse request Strip flags, resolve stable/beta/both mode, read the GitHub issue or natural-language request, and extract outcomes, acceptance, scope, constraints, and blockers.
  2. 2 Create worktree Use ak:worktree to create or reuse a clean isolated branch/worktree that matches the request.
  3. 3 Plan gates Reuse a valid existing plan or run ak:plan --tdd, then validate, red-team, and sweep whole-plan consistency before implementation.
02

Work

Agent / skill execution

  1. 4 Sync issue Create or update GitHub labels, issue body/comment, branch, route, plan link, ship mode, acceptance criteria, and plan index linkage.
  2. 5 Implement route Label in progress, then run ak:fix --auto for bugs or ak:cook --tdd --auto for feature work with the validated plan.
  3. 6 Local review Run ak:code-review --pending and fix Critical and Important findings before shipping.
03

Verify

Gate, review, validation

  1. 7 Open PR Ship beta or official PR according to mode; in both mode, beta ships first and stable waits for beta merge and green CI.
  2. 8 Review PR Run ak:review-pr with fix and reply, resolve actionable findings, and require terminal green checks unless an external blocker is documented.
  3. 9 Mark ready Apply ready-to-ship beta or stable labels to the source issue and PR, then remove stale ready-to-cook and in-progress labels.
04

Close

Report, handoff, artifact

  1. 10 Merge and converge When ship mode requests it, merge through GitHub rules, watch target-branch CI, create follow-up fix loops for deterministic failures, and close the plan index.

Syntax, arguments, subcommands

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

Syntax

/ak:vibe [--ship] [--beta] [--both] [--advice] <github-issue-url | feature request>

Arguments

<github-issue-url | feature request> Required

Issue or request

Provides the GitHub issue to treat as source of truth, or a concrete feature request that will become an issue after plan validation; it must include enough outcome, scope, constraints, and acceptance context for delivery.

/ak:vibe https://github.com/acme/app/issues/42

Shared options

--ship

Merge and converge

After PR review, fixes, replies, and green required checks, authorizes merging the PR through repository rules and watching or fixing target-branch CI until success or a documented external blocker.

/ak:vibe --ship fix flaky checkout redirect
--beta

Beta target

Ships to the beta/dev target through ak:ship beta and finishes with the ready-to-ship beta label; without --ship it stops at reviewed PR readiness.

/ak:vibe --beta https://github.com/acme/app/issues/42
--both

Beta then stable

Runs the full beta stage first, including merge and green CI, then runs the stable stage; it implies --ship and supersedes --beta when both are present.

/ak:vibe --both https://github.com/acme/app/issues/42
--advice

Kongming supervision

Adds advisory-only Kongming checkpoints after major phases, when stuck, before high-stakes decisions, and after PR CI is green; it composes with every ship mode and never bypasses gates.

/ak:vibe --advice --ship https://github.com/acme/app/issues/42

Modes / Routes

default

Stable PR readiness

Research:
Full plan gates
Review:
Required
Validate:
Review and checks
--beta

Beta PR readiness

Research:
Full plan gates
Review:
Required
Validate:
Beta review and checks
--ship

Merge and converge

Research:
Full pipeline
Review:
Required
Validate:
Post-merge CI loop
--both

Beta then stable

Research:
Two-stage pipeline
Review:
Per stage
Validate:
Beta CI before stable

Special Operations

Issue is source of truth

Issue URL inputs must match the current repo; otherwise stop and ask for the matching repo/worktree.

Dual-stage ship

Both mode runs beta to merge and green CI before stable; stable is skipped if beta remains blocked.

Advice is counsel

Kongming returns counsel, never code; the main agent remains responsible for decisions, edits, and gates.

Sample Prompt

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

PR readiness from issue Recommended 
/ak:vibe https://github.com/acme/app/issues/42
Use when:
A GitHub issue should be planned, implemented, reviewed, and labeled ready without automatic merge.
Expected:
Creates an isolated worktree, validates plan gates, ships a reviewed PR, and applies ready-to-ship stable.
Autonomous merge 
/ak:vibe --ship fix flaky checkout redirect
Use when:
A request should continue through merge and target-branch CI convergence.
Expected:
Creates or updates the issue, implements through the right route, merges, and loops on deterministic CI failures.
Beta PR readiness 
/ak:vibe --beta https://github.com/acme/app/issues/42
Use when:
The request should ship through the beta or dev target without automatic merge.
Expected:
Ships a reviewed beta-target PR, applies ready-to-ship beta, and leaves merge disabled.
Beta then stable 
/ak:vibe --both https://github.com/acme/app/issues/42
Use when:
The repo requires a beta/dev promotion before stable release.
Expected:
Completes beta merge and green CI before starting the stable stage and stable PR review.
Advisory supervision 
/ak:vibe --advice --ship https://github.com/acme/app/issues/42
Use when:
A high-stakes pipeline needs extra counsel without surrendering ownership.
Expected:
Adds kongming counsel at required checkpoints while still honoring every pipeline gate and owner decision.

Handled Scope

  • Parse request
  • Create worktree
  • Plan gates
  • Sync issue
  • Implement route
  • Local review

Related skills

Next