Stage Demo
Turns a merged GitHub pull request into a short text walkthrough that a product owner can approve or reject.
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
ghCLI, signed in. - A GitHub task server in
~/.config/robos/settings.json(thetask_serversentry 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
- 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). - Pick a PR. The app runs
gh pr viewandgh pr diff --name-onlyand saves a demo with statuspending-review. - In the list, filter by All Demos, Pending Review, Approved or Rejected. Open a demo to read its steps and Changed Files.
- 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.
- 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.