Skip to content
Page Actions
Edit this page

Repo reviews from CLI＃

You can trigger and monitor repo reviews directly from kluster-cli. This gives you a terminal-first workflow for system-wide analysis without opening the dashboard.

Prerequisites＃

Before using repo review commands from CLI, make sure you have:

  • kluster-cli installed and authenticated: See CLI quickstart.
  • A connected repository: Connect your repository in the Repo Reviews dashboard.
  • An open shell in that repository: Run commands from the repository root.

Start a repo review＃

Use this command to start a new repo-wide analysis:

kluster review repo start
verify-code-demo % kluster review repo start ✓ Repo review started for verify-code-demo. You'll receive an email when the analysis is complete.

The review runs asynchronously. You'll get an email when analysis is complete.

Check review status and results＃

Use this command to see the latest review output any time:

kluster review repo show
verify-code-demo % kluster review repo show → Last review: Fri, 13 Feb 2026 08:15:12 PST #1 HIGH performance Unbounded in-memory storage will lead to memory exhaustion (OOM). at src/endpoints.ts:13,50 More details The `reviews` array (src/endpoints.ts, line 13) is used as a global in-memory store with no size limit, TTL, or eviction policy. Fix Set a max size, use an eviction-capable cache, or move data to a persistent database. ──────────────────────────────────────────────────────────────────────── #2 HIGH security Missing CSRF protection on state-changing POST endpoint. at src/endpoints.ts:23-62 More details The '/reviews' endpoint accepts state-changing POST requests without CSRF tokens or equivalent protections. Fix Validate CSRF tokens (or enforce SameSite/custom header protections) on state-changing requests. → Repo Reviews establish a comprehensive understanding of your codebase, surfacing risks, inconsistencies, and violations that can only be detected when analyzing the code as a whole.

This output shows the last review timestamp and findings grouped by severity and category.

Next steps＃