Getting started
Examples
Warden on Warden
A review you can inspect.
This is a checked-in review fixture from Warden's own codebase. It is static on purpose: no deploy-time API key, no hidden prompt call, no fictional sample dressed up as proof. The page renders the same comment shape the CLI emits — tier, category, confidence, sources.
CommentSet
3 cited findings
context context: semantic index missing - run warden init to enable embedding-backed context selection.
packages/core/src/banner/index.ts:53 -54
An empty chunk store is treated as a missing index before model metadata is inspected.
This is the right ordering for the banner: a repository with no chunks should produce a direct `no-index` action instead of falling through into model-age or embedding checks that cannot be meaningful yet.
Keep the `chunkCount === 0` guard ahead of locked-model reads when editing this path.
packages/cli/src/index.ts:60
`warden check` still validates provider environment before any deterministic checks run.
The check command is described as deterministic-only and no-LLM, but the shared startup path calls `wardenEnv()` before acquiring the diff. Users without review credentials can be blocked before they reach the deterministic path.
Split required environment validation by mode so `check` only validates the variables it actually needs.
README.md:41 -46
Should the quick-start distinguish the optional semantic index from the required review path?
The README puts `pnpm warden init` before both `check` and `review`, while the environment table says `VOYAGE_API_KEY` is required for init and review falls back to cheap signals when it is unset. Readers may interpret embeddings as mandatory for every review.
Clarify that `init` improves review context quality but the CLI can still run without the semantic index.