Build & Spec

Code generation, the YAML spec toolchain, dependencies, i18n, entity conversion. Captured from kis --help, so this matches the binary rather than describing it.

kis code

runs cli in code generation mode

kis code [command]

Subcommand	Purpose
automation	runs the meta automation code generation commands
chunk	Structure-aware code chunks (the RAG ingestion unit)
component	runs the meta component code generation commands
form	runs the meta form code generation commands
formcontainer	runs the meta formcontainer code generation commands
formflow	runs the meta formflow code generation commands
generate-routes-js	generate javascript index js from routes yaml
get	runs the meta app code generation commands
index	Chunk code, embed the chunks, and store them in a vector store
json2entity	runs the json to entity parser
jsonschema2entity	runs the json schema to entity parser
metrics	Point-in-time structural metrics (complexity, graph shape, aggregates)
page	runs the meta page code generation commands
parse	Parse a file into lib-code’s structural model (units, imports, symbols)
plugin	runs the meta plugin code generation commands
postman2api	runs the postman to api collection parser
postman2atc	runs the postman to ATC-test-case parser
read	Read exact code by unit name or line range (how a retrieval hit is resolved)
retrieve	Semantic search over an index (embed the query, return ranked chunks)
search	Structural search (by kind/name, calls, comments, or a raw tree-sitter query)
symbols	Print a file’s symbol outline (units, depth-annotated)
update-ports	configure ports on product’s apps
update-routes	auto generate routes based on views
website	runs the meta website code generation commands
workflow	runs the meta workflow code generation commands

kis code automation

runs the meta automation code generation commands

kis code automation [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code chunk

Chunk code at structural boundaries — never splitting a unit mid-body, keeping each unit with its signature/doc and enclosing context. This is what you embed.

kis code chunk <file|dir> [flags]

Flag	Purpose
-j, --json	emit chunks as JSON
-s, --strategy string	unit

kis code component

runs the meta component code generation commands

kis code component [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code form

runs the meta form code generation commands

kis code form [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code formcontainer

runs the meta formcontainer code generation commands

kis code formcontainer [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code formflow

runs the meta formflow code generation commands

kis code formflow [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code generate-routes-js

generate javascript index js from routes yaml

kis code generate-routes-js [flags]

Flag	Purpose
-d, --dest string	destination folder (default ”./src/routes/“)
-p, --path string	path of template file to use (default ”./src/routes/routes.yaml”)

kis code get

runs the meta app code generation commands

kis code get [flags]

Flag	Purpose
-k, --context string	context to use, instead of default context (default “default”)
-d, --dest string	destination folder
-i, --input string	file path of input params in yaml format
-n, --name string	template name to retrieve
-p, --provider string	template provider, default brahma, fs is also supported (default “brahma”)
-s, --src string	source folder to load the template from, applicable only when provider is fs
-t, --type string	template type to look up. Valid values: app
-v, --version string	version to use

kis code index

Walk a path, chunk each file structurally (lib-code), embed each chunk, and upsert {vector, content, provenance} into a vector store (lib-ai).

Offline quick start (no model, no DB): kis code index ./pkg —save idx.json kis code retrieve “where do we validate edits” —load idx.json

Real embeddings + persistent store: kis code index ./pkg —provider openai —store pgvector://user:pw@localhost:5432/db kis code retrieve ”…” —provider openai —store pgvector://user:pw@localhost:5432/db

kis code index <file|dir> [flags]

Flag	Purpose
-s, --strategy string	chunk strategy: unit

kis code json2entity

this will take a uri as input and get the json from the url/file given and generate an entity out of the given json file

kis code json2entity [flags]

Flag	Purpose
-d, --destination string	name of destination file for entity generation (default “entity.yaml”)
-e, --entity string	name of entity to be generated (default “jsonentity”)
-j, --jsoninput string	link to file or file path for input json (required)

kis code jsonschema2entity

this will take a uri as input and get the jsonschema from the url/file given and generate an entity out of the given jsonschema file

kis code jsonschema2entity [flags]

Flag	Purpose
-d, --destination string	name of destination file for entity generation (default “entity.yaml”)
-e, --entity string	name of entity to be generated (default “jsonentity”)
-j, --jsoninput string	link to file or file path for input json (required)

kis code metrics

Point-in-time structural metrics (complexity, graph shape, aggregates)

kis code metrics <file|dir> [flags]

Flag	Purpose
-j, --json	emit metrics as JSON

kis code page

runs the meta page code generation commands

kis code page [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code parse

Parse a source file with tree-sitter and print its structural model. Reads stdin when no file is given.

kis code parse <file> [flags]

Flag	Purpose
-j, --json	emit the full model as JSON

kis code plugin

runs the meta plugin code generation commands

kis code plugin [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis code postman2api

this will take a postman api as an input and parse through each folder/request to create individual folders/api reqests collection files inside desination path provided

kis code postman2api [flags]

Flag	Purpose
-d, --dest string	destination folder for ATC test cases generation (default ”./api”)
-n, --name string	custom name for root folder
-t, --timeout string	custom timeout to wait for api information from postman link provided (default “2m”)
-u, --upload string	postman collection API link (required)

kis code postman2atc

this will take a postman api as an input and parse through each folder/request to create individual folders/atc yaml test cases inside desination path provided

kis code postman2atc [flags]

Flag	Purpose
-d, --dest string	destination folder for ATC test cases generation (default ”./tests/functional”)
-n, --name string	custom name for root folder
-t, --timeout string	custom timeout to wait for api information from postman link provided (default “2m”)
-u, --upload string	postman collection API link (required)

kis code read

Given provenance (a file + a unit/lines, e.g. from kis code retrieve), print the exact code.

kis code read <file> [flags]

Flag	Purpose
-L, --lines string	line range A:B (1-based, inclusive)
-u, --unit string	unit name (or qualified name) to print

kis code retrieve

Semantic search over an index (embed the query, return ranked chunks)

kis code retrieve <query...> [flags]

Flag	Purpose
-j, --json	emit results as JSON
-k, --top int	number of results (default 5)

kis code search

Find code by structure, not text. Examples: kis code search ./pkg —kind function —name ‘Handle*’ kis code search ./pkg —calls dangerousFn kis code search ./pkg —raw ‘(type_spec name:(type_identifier)@n type:(struct_type))@struct’

kis code search <file|dir> [flags]

Flag	Purpose
-j, --json	emit matches as JSON

kis code symbols

Print a file’s symbol outline (units, depth-annotated)

kis code symbols <file> [flags]

Flag	Purpose
-j, --json	emit outline as JSON

kis code update-ports

auto confugures the ports in the apps running inside the product

kis code update-ports [flags]

Flag	Purpose
-k, --context string	name of the context to use to login (default “default”)
-p, --path string	location to the vite config file to configure the port

kis code update-routes

auto generates js route files based one for each file that is present in the views source dir

kis code update-routes [flags]

Flag	Purpose
-d, --dest string	location of routes js files destination folder (default ”./src/routes/“)
-r, --route string	location where the template is to be saved (default ”./src/routes/routes.yaml”)
-p, --src string	location of the views from which the paths are to be generated (default ”./src/views/“)

kis code website

runs the meta website code generation commands

kis code website [flags]

Flag	Purpose
-k, --key string	template@version
-t, --template string	template to use
-v, --version string	version to use
-w, --website string	website name

kis code workflow

runs the meta workflow code generation commands

kis code workflow [flags]

Flag	Purpose
-f, --file string	file name to use
-k, --key string	template@version:path
-p, --path string	path of template file to use
-t, --template string	template to use
-v, --version string	version to use

kis spec

Commands for working with kis.ai YAML specifications.

Provides validation, linting, scaffolding, and schema operations for Entity, Workflow, Route, Pipeline, Agent, Policy, and other YAML definitions.

Examples: kis spec validate entities/order.yaml kis spec lint entities/ kis spec new entity order kis spec list kis spec schema Entity

kis spec [command]

Subcommand	Purpose
generate	Generate artifacts from definitions
lint	Check for best practice violations
list	List registered kinds and versions
new	Scaffold new YAML definitions
schema	View schema definitions
validate	Validate YAML files against schemas

Flag	Purpose
-v, --verbose	Verbose output

kis spec generate

Generates various artifacts from YAML definitions and schemas.

Supported generation types: jsonschema - Generate JSON Schema files docs - Generate documentation (markdown)

Examples: kis spec generate jsonschema —output ./schemas kis spec generate jsonschema —kind Entity —output ./schemas kis spec generate docs —output ./docs

kis spec generate <type> [flags]

Flag	Purpose
-o, --output string	Output directory

kis spec lint

Checks YAML files for best practice violations beyond schema compliance.

Lint rules enforce naming conventions, required fields, and other best practices that improve consistency and maintainability.

Examples: kis spec lint entities/order.yaml kis spec lint —rules naming-convention,description-required entities/ kis spec lint —list-rules kis spec lint —fix entities/ kis spec lint —ignore description-required entities/

kis spec lint [files...] [flags]

kis spec list

Lists all registered YAML kinds and their versions.

Shows both user-facing definitions (Entity, Workflow, etc.) and internal configuration types.

Examples: kis spec list kis spec list —verbose kis spec list —category definition kis spec list —category config kis spec list —format json

kis spec list [flags]

kis spec new

Creates new YAML definition files from templates.

Supports scaffolding for all registered kinds including Entity, Workflow, Route, Pipeline, Agent, and Policy.

Examples: kis spec new entity order kis spec new entity —template commerce order kis spec new workflow order-approval kis spec new entity -o entities/order.yaml order kis spec new entity —dry-run order

kis spec new <kind> [name] [flags]

Flag	Purpose
-o, --output string	Output file path

kis spec schema

Displays schema information for a specified kind.

Shows field definitions, types, and documentation. Can output as human-readable text, JSON Schema, or CUE format.

Examples: kis spec schema Entity kis spec schema Entity —version v2 kis spec schema Entity —format jsonschema kis spec schema Entity —field spec.fields

kis spec schema <kind> [flags]

kis spec validate

Validates YAML files against their schemas.

The schema is auto-detected from the file’s ‘kind’ field. Supports validation of single files, multiple files, and directories.

Examples: kis spec validate entities/order.yaml kis spec validate entities/ kis spec validate —cross-ref entities/ workflows/ kis spec validate —version v2 entities/order.yaml kis spec validate —format json entities/

kis spec validate [files...] [flags]

kis i18n

consumes kisai i18n files to generate ftl files

kis i18n [flags]

Flag	Purpose
-d, --dir string	localisation dir to consume and output ftl files (point to i18n folder in product, defaults to current folder) (default ”.”)

kis yaml

Format-preserving YAML editing with atomic writes, schema validation, and audit trail support.

kis yaml [command]

Subcommand	Purpose
delete	Delete a node at a YAML path
get	Get a value at a YAML path
set	Set a value at a YAML path
validate	Validate a YAML file against a schema

kis yaml delete

Delete removes the node at the specified path. Same atomicity guarantees as set.

kis yaml delete [flags]

Flag	Purpose
-v, --verbose	Emit progress to stderr

kis yaml get

Get returns the scalar value at the specified path, or the YAML representation of a subtree for non-scalar nodes.

kis yaml get [flags]

kis yaml set

Set updates the value at the specified path in a YAML file. The file is updated atomically — either fully updated or fully untouched. Idempotent: no-op if the current value already matches.

kis yaml set [flags]

Flag	Purpose
-v, --verbose	Emit progress to stderr

kis yaml validate

Validate checks a YAML file against a JSON Schema or CUE schema. Returns exit code 0 on success, 3 if validation errors are found.

kis yaml validate [flags]

kis liquid

process liquid template file

kis liquid [flags]

Flag	Purpose
-o, --outputfile string	output file path
-t, --template string	liquid template file path
-v, --varFile string	environment yaml file path
-c, --vars stringToString	variables (default [])