Quick Ref / Command

Engineer Kit

/ak:test

Engineering Test and QA

Runs and designs unit, integration, e2e, UI, coverage, build, visual regression, suite-creation, suite-optimization, and deceptive-test audit workflows for engineering quality.

01

Select operation

02

Identify scope

03

Load workflow reference

04

Run early checks

Rule 01

Test behavior, not plumbing

Rule 02

Critical paths need happy-path and error coverage

Rule 03

Tests must be deterministic, isolated, and reproducible

Rule 04

UI QA includes screenshots, responsive checks, accessibility, forms, and console errors

Execution Map

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

01

Start

Input, scope, route

  1. 1 Select operation With no arguments, present default, ui, create, optimize, and audit options; with context, proceed to the matching test scope.
  2. 2 Identify scope Use recent changes, requirements, coverage thresholds, UI needs, build concerns, or CI pain to choose the workflow.
02

Work

Agent / skill execution

  1. 3 Load workflow reference Load code execution, UI testing, report format, create-suite, optimize-suite, or audit-suite guidance as appropriate.
  2. 4 Run early checks Run typecheck or analyze commands first when they catch syntax and static errors before slower suites.
03

Verify

Gate, review, validation

  1. 5 Execute tests Use the project runner for unit, integration, e2e, coverage, build, or UI/browser verification.
  2. 6 Analyze failures Focus on failing tests, error chains, logs, screenshots, console errors, and root causes rather than pass counts alone.
04

Close

Report, handoff, artifact

  1. 7 Create or improve suites For create, optimize, or audit, scout coverage, CI, history, and docs, then implement coverage, speed, or trust improvements.
  2. 8 Report QA result Produce a structured report with results, coverage, failed tests, performance/build status, recommendations, and team-mode completion state when relevant.

Syntax, arguments, subcommands

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

Syntax

/ak:test [context]

or

/ak:test ui [url]

or

/ak:test <create|optimize|audit> [scope] [--advice] [--ultra] [--interview]

Arguments

[context]

Validation context

Describes the change, requirement, failing area, affected module, command, coverage threshold, or time boundary that should determine the smallest useful code-test scope. Omit it to choose an operation interactively.

/ak:test "Validate the session expiry change: run typecheck, focused session tests, affected integration tests, and coverage for the changed module."

Subcommands

ui UI validation
/ak:test ui [url]

Runs the browser-oriented workflow for a website or app screen, including page discovery, screenshots, responsive behavior, accessibility, forms, console findings, and selected flows.

[url]
Target page to inspect. Include expected state, viewport, authentication approach, and data-safety limits in the request when they matter.

Outcome: Structured UI QA evidence with tested pages and flows, screenshot paths, console findings, viewports, skipped browser checks, critical issues, and limits.

/ak:test ui http://localhost:3000/settings
create Create suite
/ak:test create [scope] [--advice] [--ultra] [--interview]

Scouts code and docs, builds a coverage matrix, then creates or extends tests for a feature or workflow without testing irrelevant lines just to raise a percentage.

[scope]
Feature, workflow, critical path, existing framework, or project threshold the new suite should cover.
--advice
Adds Kongming advice after analysis, before suite or CI edits, and when stuck. Advice cannot bypass failing-test rules.
--ultra
Runs five read-only candidates in one parallel wave and has a verifier select one suite design unchanged or reject all.
--interview
Presents proposed test and CI change groups before applying them, then applies only approved groups.

Outcome: A meaningful suite or extension tied to a coverage matrix, with evidence that critical behavior and error paths are covered.

/ak:test create "Cover the account recovery workflow" --interview
optimize Optimize suite
/ak:test optimize [scope] [--advice] [--ultra] [--interview]

Analyzes CI, git history, code, and docs to reduce test time or cost while preserving safety-critical coverage.

[scope]
Slow job, CI timing evidence, safety-critical group, or allowed workflow change to optimize.
--advice
Adds Kongming advice after analysis, before suite or CI edits, and when stuck. Advice cannot approve lost coverage.
--ultra
Runs five read-only candidates in one parallel wave and has a verifier select one optimization plan unchanged or reject all.
--interview
Presents proposed test and CI change groups before applying them, then applies only approved groups.

Outcome: A faster or cheaper suite with unchanged safety guarantees, change list, and evidence for any CI workflow edits.

/ak:test optimize "Reduce pull-request CI time" --advice
audit Audit suite
/ak:test audit [scope] [--advice] [--ultra] [--interview]

Searches the suite and CI for deceptive, disabled, unfinished, ineffective, redundant, outdated, or unsafe tests, then repairs evidence-backed findings.

[scope]
Suite, CI area, trust concern, known skip, or security-sensitive path to inspect.
--advice
Adds Kongming advice after findings, before repairs, and when stuck. Advice cannot replace evidence.
--ultra
Runs five read-only candidates and returns the evidence-validated, deduplicated union of findings before repairs.
--interview
Presents proposed test and CI repair groups before applying them, then applies only approved groups.

Outcome: Evidence-backed weak-test findings, deduplicated repair plan, applied approved repairs, and remaining trust or product-root-cause handoff notes.

/ak:test audit "Check skipped and ineffective authorization tests" --ultra

Output / publish flags

Only flags that change the artifact or publish it. Not the full option set.

--advice

Kongming advice

Adds advisory-only checkpoints after analysis, before suite/CI edits, and when stuck.

Example

/ak:test audit suite --advice
--ultra

Ultra verifier

For create, optimize, or audit, runs five read-only candidates and a strongest-model verifier before implementation.

Example

/ak:test create billing --ultra
--interview

Interview changes

Before applying changes, presents proposed test/CI edits by group and applies only approved groups.

Example

/ak:test optimize CI --interview

Modes / Routes

default

Code tests

Research:
Changed scope
Review:
Failures/root cause
Validate:
Runner + coverage
ui

UI tests

Research:
Page state
Review:
Console/a11y/responsive
Validate:
Browser evidence
create

Create suite

Research:
Coverage matrix
Review:
Uncovered contracts
Validate:
New meaningful tests
optimize

Optimize suite

Research:
CI/history/docs
Review:
Lost coverage risk
Validate:
Equal safety faster
audit

Audit suite

Research:
Suite + CI
Review:
Weak/deceptive tests
Validate:
Trust repairs

Sample Prompt

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

Run changed-scope tests Recommended
/ak:test checkout payment flow
Use when:
Use after implementation or a bug fix when a validation suite should run for a concrete scope.
Expected:
Identifies the relevant scope, runs early typecheck/analyze commands when useful, executes the matching project suites, treats failures as blockers, and returns a structured QA summary.
Check a live UI
/ak:test ui http://localhost:3000/checkout
Use when:
Use when a website or app screen needs visual, responsive, accessibility, form, or console-error validation.
Expected:
Loads the UI testing workflow, uses browser-capable tooling or project-native browser tests, captures the relevant evidence, and reports UI QA findings in the standard format.
Create missing coverage
/ak:test create auth module --ultra
Use when:
Use when a feature area lacks meaningful tests and needs a designed validation suite.
Expected:
Scouts the codebase and docs, builds a coverage matrix, runs the ultra best-of-5 verifier for the design, then implements the selected test suite once.
Optimize CI testing
/ak:test optimize CI suite --interview
Use when:
Use when test cost or runtime is high and suite/CI changes should be approved before applying.
Expected:
Parallel-scouts CI/CD, git history, codebase, and docs; proposes speed or cost reductions that preserve safety; and applies only approved change groups.
Audit weak tests
/ak:test audit frontend tests --advice
Use when:
Use when a suite may contain skipped, deceptive, redundant, outdated, unfinished, or security-gap tests.
Expected:
Parallel-scouts the suite and CI, gathers evidence for weak or deceptive tests, asks Kongming for advisory checkpoints, then repairs validated issues without bypassing failing-test gates.

Handled Scope

  • unit and integration
  • e2e
  • UI/browser testing
  • coverage
  • suite creation
  • CI optimization
  • test audit

Next