Skip to main content
ClaudeWave
Slash Command975 estrellas del repoactualizado today

loki-verify

The loki-verify command executes Loki's deterministic verification suite against the current change, comparing it to a specified base branch (defaulting to main), and reports the complete verdict with supporting evidence from build, test, static analysis, secret scanning, dependency audit, and specification drift checks. Use this command when you need an auditable, evidence-based assessment of code quality and safety that refuses to silently pass inconclusive findings, distinguishing it from opinion-based chat feedback by delivering machine-readable evidence artifacts and explicit verdict classifications.

Instalar en Claude Code
Copiar
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/asklokesh/loki-mode/HEAD/.claude/commands/loki-verify.md -o ~/.claude/commands/loki-verify.md
Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

loki-verify.md

Run Loki's Autonomi Verify on the current working tree and report the verdict
with its evidence, not just an opinion in chat. The differentiator is the
auditable artifact: a verdict that refuses to silently pass on inconclusive
evidence.

Steps:

1. Run the verifier against the base ref ($ARGUMENTS, or `main` if empty):

   ```
   loki verify $ARGUMENTS
   ```

   It computes the PR-style delta merge-base(base, HEAD)..HEAD and runs
   deterministic gates (build, tests, static analysis, secret scan, dependency
   audit, and spec drift when a spec lock exists). Exit codes:
   0 VERIFIED, 1 CONCERNS, 2 BLOCKED, 3 verifier error.

2. Read the evidence artifacts it wrote:
   - `.loki/verify/evidence.json` (machine-readable: schema, gates, findings)
   - `.loki/verify/report.md` (human verdict + findings table)

3. Summarize for the user:
   - The verdict (VERIFIED / CONCERNS / BLOCKED) and exit code.
   - Each gate and its status (pass / fail / inconclusive / skipped).
   - Every finding: severity, category, file:line, and whether it is blocking.
   - If the verdict is CONCERNS or BLOCKED, list exactly what to fix.

Be honest about inconclusive evidence: an inconclusive gate (for example a test
runner that could not run) is never upgraded to VERIFIED. If the diff is empty,
the verdict is CONCERNS (nothing to verify), not VERIFIED. Do not claim the
change is verified unless the evidence says VERIFIED.