// Run a live Looper-Go smoke test by creating a temporary project (PROJECT.md + to-do.json), executing looper for one iteration, observing output, and reporting results. Use when verifying looper-go behavior or demonstrating a live run.
| name | looper-live-test |
| description | Run a live Looper-Go smoke test by creating a temporary project (PROJECT.md + to-do.json), executing looper for one iteration, observing output, and reporting results. Use when verifying looper-go behavior or demonstrating a live run. |
Run a real looper-go iteration in a fresh temp directory to validate task selection and summary application, then report what happened.
looper binary. Prefer looper on PATH; otherwise set LOOPER_BIN to a specific path (for example ~/looper-go/bin/looper or go run github.com/nibzard/looper-go/cmd/looper).~/.claude/skills/looper-live-test/scripts/run-live-test.shTask: line and Summary: line.to-do.json and any created files.PROJECT.md.to-do.json with tasks T10 and T2 (both priority 1).MAX_ITERATIONS=1 looper runto-do.json and created files.looper run as the main command (not looper.sh to-do.json).looper/config.json, environment, or CLI flagslooper-logs/runs/<run-id>/events.jsonllooper doctor to check dependencies and configurationLooper-Go development workflows: build, test, run, debug, and manage the looper-go project. Use when working on looper-go codebase, running tests, building binaries, or debugging issues.
Run a live Looper-Go smoke test by creating a temporary project (PROJECT.md + to-do.json), executing looper for one iteration, observing output, and reporting results. Use when verifying looper-go behavior or demonstrating a live run.
Looper-Go development workflows: build, test, run, debug, and manage the looper-go project. Use when working on looper-go codebase, running tests, building binaries, or debugging issues.