Stage Demo

Stage Demo Viewer is a review queue for merged work. For each merged pull request you generate a “demo”: a record with the PR details and a text walkthrough, which someone then marks approved or rejected. Despite the name, it does not record video, narrate or deploy anything.

Requirements

• The gh CLI, signed in.
• A GitHub task server in ~/.config/robos/settings.json (the task_servers entry that is active, or the first). Other task server types are refused with “GitHub task server required”. You can configure one in Task Servers.

Use it

1. Click New Demo. The panel Generate Demo from Merged PR lists the last 20 merged PRs of each repository on the task server (gh pr list --state merged).
2. Pick a PR. The app runs gh pr view and gh pr diff --name-only and saves a demo with status pending-review.
3. In the list, filter by All Demos, Pending Review, Approved or Rejected. Open a demo to read its steps and Changed Files.
4. Click Approve or File Bug / Reject. Either one only sets the demo’s status and review time. Rejecting does not create an issue, so file the bug yourself.
5. View PR on GitHub opens the pull request in your browser. The refresh button reloads the list.

What the walkthrough contains

The steps are generated by a fixed template, not by a language model: “What Changed” (PR title, author, lines changed, file count), the first 500 characters of the PR description, one step per top-level folder listing up to ten changed files, and a closing “Verification” step that asks the reviewer to check the changes.

Where data lives

Each demo is a JSON file at ~/.config/robos/stage-demos/demo-<id>.json.

Run it

Launch Stage Demo Viewer from the app launcher, or run npm start in packages/stage-demo. For recorded, narrated proof-of-work, see Walkthroughs and proof of work.