test-gate

test-gate

Claude Code can write the checklist. test-gate gives you a shared place to run it.

Run a gate Read the schema
Renders a JSON test-session as a focused checklist.
Captures human test results without terminal archaeology.
Writes a result artifact Claude Code can read next session.
The test-gate app showing a session sidebar, a selected verification item, status buttons, notes, and screenshot capture.

Claude Code can author the gate. Running it is where the workflow breaks.

The AI can generate a serious release checklist. Then the human has to test it by scrolling through terminal history, hunting for the current item, copy-pasting notes, and explaining findings back into chat.

Terminal chat handoff

  • ×Session and item IDs get buried in a long Claude Code transcript.
  • ×The human scrolls up and down to find what to test next.
  • ×Status, notes, screenshots, and findings are copy-pasted back by hand.
  • ×The next Claude Code session has to reconstruct what really happened.

Shared gate workspace

  • ✓Claude Code authors the run JSON from the release plan.
  • ✓The browser shows one focused checklist item at a time.
  • ✓Pass, fail, CR, notes, and screenshots attach to the right item.
  • ✓The same JSON becomes the shared discussion and resume artifact.

A gate workflow that survives context switches.

Keep the human in the loop, but stop using the chat scroll as the database.

1

Author

Ask Claude Code to turn a release plan into sessions, items, rationale, and expected outcomes.

/test-gate:new
2

Run

Open the local browser cockpit instead of reading the checklist inside the terminal transcript.

/test-gate:run
3

Capture

Click status, add notes, paste screenshots, and promote findings without leaving the flow.

auto-save
4

Resume

Let Claude Code digest the finished run: fail agenda, CR backlog, findings, and next step.

/test-gate:results

Dogfood proof from a real release gate.

The first internal gate replaced terminal scrolling with a single-screen verification cockpit and produced a clean, resumable artifact.

Vibalos 0.8.5 gate
22/22 PASS Completed locally during the 2026-05-05 live-test gate.
Game-Changer · Mehrwert immens hoch
Vibalos dogfood feedback

Built for local-first developers.

test-gate is intentionally small: no cloud account, no team management surface, no CI ceremony before the schema has earned it.

JSON-first

The run file contains sessions, items, statuses, notes, screenshots, and findings.

Git-committable

Results live in the repo, so the audit trail is reviewable and reproducible.

No cloud. No auth.

Everything stays on your machine. No accounts, telemetry, or remote sync.

Same-origin server

A Bun server serves the static UI and API together on localhost.

Claude Code plugin

Slash commands author, run, and digest gates where the checklist came from.

Install the Claude Code plugin, then run a gate.

The plugin gives Claude Code the author-run-results loop. The browser UI writes every status, note, finding, and screenshot back to the run JSON. 

/plugin marketplace install moinsen-dev/test-gate
/plugin install test-gate@moinsen-test-gate

# then:
/test-gate:new docs/release-plans/next-release.md
/test-gate:run .test-gate/next-release.json
/test-gate:results .test-gate/next-release.json