dxkit-loop

dxkit-loop

This skill owns the loop pack: the deterministic preflight/postflight layer that keeps an autonomous coding loop from declaring "done" while it has introduced net-new findings. Reach for it to set the gate up, to explain a block, or to tune the posture.

What the loop pack is

When Claude Code runs in a loop (it keeps working until it decides to stop), a Stop hook runs vyuh-dxkit hook stop-gate every time the agent tries to stop. The gate re-runs the guardrail check against the baseline and:

• net-new findings → blocks the stop and feeds the exact findings back to the model so it repairs them, then tries to stop again;
• clean → allows the stop (optionally after a configured test command passes);
• gate can't run (no baseline / config error) → blocks once for the operator (a problem the model can't fix), then allows on the next attempt to avoid thrashing.

Every Stop event is appended to an audit trail at .dxkit/loop/ledger.jsonl.

The value is predictability, not a new scanner: the gate bounds the "loop shipped debt and never fixed it" failure mode to zero. It uses the same findings, baseline, and identity contract as the rest of dxkit — it does not detect anything new.

See it first (no setup)

# No API key, no Claude Code, no scanners — runs the real gate over an example
# finding and shows the block → repair → clean flow offline.
npx vyuh-dxkit demo loop-guardrail

Setup

# Register the Stop hook + CLAUDE.md loop norm + default preset.
# Additive: merges into existing .claude/settings.json + CLAUDE.md,
# never clobbering your hooks or prose.
npx vyuh-dxkit init --claude-loop

# Pick the posture up front (default is security-only):
npx vyuh-dxkit init --claude-loop --loop-preset full-debt

A loop is only safe if a baseline exists, the hook is registered, and the guardrail can run. Always verify before an unattended run:

npx vyuh-dxkit loop doctor

It checks: git repo, baseline present/resolvable, Stop hook registered, active preset, optional postflight test command, graph freshness. Exit non-zero = not safe to run unattended yet — each failing check carries a fix command. The most important one it catches is the silent failure: an unregistered hook never fires, so the loop would run with no gate and no error. If loop doctor says the baseline is missing, capture one first (npx vyuh-dxkit baseline create).