From lacp-hardening
Displays LACP hardening status including active hooks, context mode, eval checkpoint state, and recent quality gate decisions for the current directory.
How this command is triggered — by the user, by Claude, or both
Slash command
/lacp-hardening:hardening-statusThe summary Claude sees in its command listing — used to decide when to auto-load this command
Show the current LACP hardening status by checking: 1. **Active hooks**: Which LACP hooks are installed and firing 2. **Context mode**: What `LACP_CONTEXT_MODE` is set (if any) 3. **Eval checkpoint**: Whether continuous QA is enabled and its last result 4. **Quality gate**: Recent telemetry decisions (blocks, allows, scores) 5. **Handoff**: Whether a handoff artifact exists for this directory Run these commands to gather the data: Present the results as a clear status report.
Show the current LACP hardening status by checking:
LACP_CONTEXT_MODE is set (if any)Run these commands to gather the data:
# Check hook telemetry (last 5 entries)
tail -5 ~/.local/share/claude-hooks/telemetry.jsonl 2>/dev/null | python3 -c "
import json, sys
for line in sys.stdin:
try:
e = json.loads(line.strip())
print(f\" {e.get('ts','?')[:19]} {e.get('hook','?'):10s} {e.get('decision','?'):6s} {e.get('reason','')[:60]}\")
except: pass
" || echo " No telemetry data"
# Check eval checkpoint
cat ~/.lacp/hooks/contracts/*/eval_checkpoint.json 2>/dev/null | python3 -c "
import json, sys
try:
d = json.load(sys.stdin)
print(f\" Writes: {d.get('write_count',0)}, Last: {d.get('last_result','?')}, Fails: {d.get('fail_count',0)}\")
except: print(' No checkpoint data')
"
# Check context mode
echo " Mode: ${LACP_CONTEXT_MODE:-none}"
echo " Eval checkpoint: ${LACP_EVAL_CHECKPOINT_ENABLED:-disabled}"
Present the results as a clear status report.
npx claudepluginhub 0xnyk/lacp --plugin lacp-hardening/harness-statusDisplays the current health of the project's harness — enforcement ratio, drift, and garbage collection state by reading HARNESS.md.
/doctorRuns a comprehensive diagnostic on pro-workflow setup, hooks, context usage, MCP servers, CLAUDE.md size, git status, and settings to identify configuration issues.
/selftestRuns ClawdStrike self-test to verify all components are operational, reporting PASS/FAIL for each of 6 checks and an overall score.
/validate-hookValidates Claude Code hooks against security, performance, and SDK compliance criteria. Produces pass/fail scores and supports selective checks and auto-fix.
/preflightRuns pre-flight validation checks on the current tool context, file, or command. Also supports policy listing, single-use bypass, and status display.
/doctorRuns a health check on the great_cto pipeline, reporting missing files, format issues, hook status, and permission errors. Accepts --fix to emit remediation commands.