Help us improve
Share bugs, ideas, or general feedback.
From deepest-plan
CLI platform validation via direct binary execution. Captures stdout, stderr, exit codes, file output, pipe behavior. Cited as platform_skill on CLI gates in deepest-plan output.
npx claudepluginhub krzemienski/deepest-plan-plugin --plugin deepest-planHow this skill is triggered — by the user, by Claude, or both
Slash command
/deepest-plan:cli-validationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Command-line binary validation (Rust `cargo`, Go, Bun-compiled, Python scripts, Node CLI tools). Does NOT handle API servers (use `api-validation`) or GUI apps (use `web-validation` / `ios-validation`).
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Command-line binary validation (Rust cargo, Go, Bun-compiled, Python scripts, Node CLI tools). Does NOT handle API servers (use api-validation) or GUI apps (use web-validation / ios-validation).
cargo --version, go version, bun --version, etc.)build / cargo build --release / go build exits 0test -x)# Capture stdout + stderr + exit code + timing in one pass
./target/release/mytool process --input ./fixtures/sample.csv --output ./out.json \
2>e2e-evidence/vgN-stderr.log \
> e2e-evidence/vgN-stdout.log
EXIT=$?
echo "exit=$EXIT" >> e2e-evidence/vgN-stdout.log
# Also capture the output file
cp ./out.json e2e-evidence/vgN-out.json 2>/dev/null || true
Good:
Processed 150 rows in"rows == 150 AND errors == 0"Bad (reject):
<validation_gate id="VG-N" blocking="true" platform="cli"
protocol="functional-validation"
platform_skill="cli-validation"
verdict_by="gate-validation-discipline">
<preflight skill="preflight">[build clean + binary executable]</preflight>
<execute>[./binary with real inputs; capture stdout/stderr/exit/artifacts]</execute>
<capture>[all to e2e-evidence/vgN-*]</capture>
<pass_criteria>[exit code + specific stdout strings + artifact checks]</pass_criteria>
<review>[grep for markers; jq on output JSON; stat output files]</review>
<verdict>PASS → next | FAIL → error-recovery → re-run</verdict>
<mock_guard skill="no-mocking-validation-gates">
No mocking stdin/stdout, no test-only flags, no dry-run for validation gates.
</mock_guard>
</validation_gate>
echo data | ./tool → correct behavior| Symptom | Likely cause | Fix |
|---|---|---|
| Exit 0 but wrong output | Silent error swallowed | Check return paths; propagate errors |
| Exit non-zero but no stderr | Panic before log init | Wire stderr logging first |
| Works on test inputs, crashes on real | Hardcoded assumption | Add input validation with clear error |
| Slow on large inputs | O(n²) in hot path | Profile before shipping |
CLIs may take secrets as args or env vars. Never log evidence containing real secrets; use placeholders when building fixture inputs.