27 tagged code documentation, measured the same way as everything else here.
Browse within: documentation 12markdown 12adr 8annotations 8cli-tool 6
Command
Deploy telemetry upstream after build. Expects skene-context/engine.yaml, skene-context/feature-registry.json (or configured outputdir; legacy skene/feature-registry.json still works), and supabase/migrations/skenetriggers.sql; push uploads the package to Skene Cloud.
Command
Initialize Skene configuration for this project. Creates .skene.config (TOML), sets up provider and API key (or SKENEAPIKEY), and runs validation.
Command
Check implementation status from skene-context/engine.yaml. Validates features, action vs code-only mode, and that trigger/function SQL exists in migrations; detail shows latest matching file and (+N) if duplicates.
Command
Use this command only when the user explicitly asks to initialize or refresh project agent documentation.
Command
Record why the code is the way it is, bound to the code.
Command
Set koment up in a repository that does not have it yet.
Command
Turn an existing source comment into an annotation and remove it.
Command
This page documents how the livewiki batch command is registered with the Commander CLI framework and how it formats batch run reports for human consumption.
Command
The livewiki export command turns the project's curated wiki into a deliverable artifact on disk: either a flattened snapshot under .livewiki/export/ / (for generic, github-wiki, and gitlab-wiki targets) or a synthesized repository-root README.md (for the readme target).
Command
This page explains how the livewiki install CLI command detects installed coding agents and safely configures the livewiki MCP server entry, hook templates, shared skills, and optional pointer files.