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

Implementation Recap

Summarizes completed engineering work, evidence, failures, trade-offs, behavior, architecture, usage, and follow-ups without replaying the full session.

01

Gather evidence

02

Separate evidence states

03

Highlight relevant substance

04

Add a clarifying visual

Rule 01

Evidence first, narrative second

Rule 02

Verified is not the same as proposed

Rule 03

Use visuals only when they clarify

Rule 04

Keep unresolved work last and actionable

Execution Map

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

01

Start

Input, scope, route

  1. 1 Gather evidence Use the conversation, accepted decisions, current diff, tests, and relevant issue or plan state as the strongest available evidence.
  2. 2 Separate evidence states Separate implemented and verified work from proposed, inferred, untested, unshipped, or still-unresolved work.
02

Work

Agent / skill execution

  1. 3 Highlight relevant substance Summarize outcomes, high-value changes, failures and workarounds, decisions, how the result works, practical usage, follow-ups, and next steps.
  2. 4 Add a clarifying visual Use a compact table, chart, Mermaid diagram, or ASCII flow when it clarifies behavior, user flow, architecture, database, or UI/UX; otherwise briefly say why no visual helps.
03

Verify

Gate, review, validation

  1. 5 Keep unresolved work last Keep the recap concise, use the user's language, omit empty sections, and put unresolved items last.

Syntax, arguments, subcommands

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

Syntax

/ak:sumup [task|PR|branch|recent]

Arguments

[task|PR|branch|recent]

Recap scope

Optional evidence boundary: one task, a pull request, a branch, or recent work. Omit it to recap the strongest nearby implementation evidence. It does not implement, deploy, or replace a live status check.

/ak:sumup recent

Subcommands

task Task recap
/ak:sumup task

Recap one completed task: outcome, verified changes, failures, decisions, and remaining work.

Outcome: A concise task recap with evidence boundaries and unresolved items last.

/ak:sumup task
PR Pull request recap
/ak:sumup PR

Recap the implemented work bounded by a pull request without claiming it is deployed.

Outcome: PR-bounded highlights, verification state, and follow-ups without a deployment claim.

/ak:sumup PR
branch Branch recap
/ak:sumup branch

Recap implemented work on the named or current branch using diff, tests, and accepted decisions.

Outcome: Branch-scoped outcome, key changes, failures, and remaining blockers with evidence named.

/ak:sumup branch
recent Recent work recap
/ak:sumup recent

Recap the most recent implementation period without replaying the whole session.

Outcome: Recent-work recap that separates verified results from untested or unresolved items.

/ak:sumup recent

Sample Prompt

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

Default recap Recommended 
/ak:sumup
Use when:
After implementation, when a human needs the outcome without replaying the work session.
Expected:
Produces a concise recap with outcome, strongest nearby evidence, key implemented changes, verification boundaries, unresolved blockers, and actionable next steps last.
Task recap 
/ak:sumup task
Use when:
One completed task needs an evidence-bounded recap of what changed and what remains.
Expected:
Summarizes that task's outcome, verified changes, failures and workarounds, decisions, and remaining blockers without implementing anything new.
Pull request recap 
/ak:sumup PR
Use when:
The pull request is the evidence boundary and must not be treated as a live deploy.
Expected:
Recaps PR-bounded implemented work, separates verified from untested changes, and refuses to claim deployment without runtime evidence.
Branch recap 
/ak:sumup branch
Use when:
You need the implemented story of the current or named branch without a live status check.
Expected:
Uses branch diff, tests, and accepted decisions as evidence, explains how the result works when useful, and keeps unresolved items last.
Recent work recap 
/ak:sumup recent
Use when:
The latest implementation period should be recapped without replaying the whole session.
Expected:
Gathers recent conversation, diff, and test evidence, omits empty sections, and adds a compact visual only when it clarifies behavior or architecture.

Handled Scope

  • implementation recap
  • verification summary
  • failure recovery
  • architecture explanation
  • follow-up prioritization

Next