messhall-tape-qa
Skill1 starsChanged 35 days agoMITView on GitHub
Record QA proof for Messhall's CLI, daemon and MCP work with vhs, one tape per QA case. Tapes are committed under demo/tapes/, gifs and mp4s render to the gitignored demo/out/, the gif goes to the qa-assets branch with pnpm messhall-dev qa-upload and into the PR's "QA and Testing" section as a 2-column table (case plus exit code extras, recording). Use when the user says "tape qa", "record the cli", "add a recording to the PR", "vhs the cli", "show the command in the PR", or invokes /messhall-tape-qa.
- Installs packages
In this repository6 other files it gives its agents.
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- messhall-controlSkill
- messhall-pickup-any-workSkill
- musterSkill
- using-messhallSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run tapes from the worktree you are proving, with pnpm dev <command> or pnpm messhall-dev <command>, so the recording shows the branch and …
- Very specific: line 18
Read the PR's description (gh pr view <n> -R maximilianfalco/messhall --json body -q .body).
- Very specific: line 24
Keep the Set block (zsh, FontSize 18, Width 1400, Height 820, Padding 24, Catppuccin Mocha, TypingSpeed 40ms) so every recording looks the …
- Distinctive: line 39
Never record a key file, a real room transcript or anything from the real data dir.
- Very specific: line 64
Always pass -R maximilianfalco/messhall.
- Distinctive: line 65
Write in the owner's voice: lowercase starts, plain words.
- Very specific: line 69
Check the rendered body: gh api repos/maximilianfalco/messhall/issues/<n> -H 'Accept: application/vnd.github.full+json' --jq .body_html | …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
messhall-tape-qa
Turn each case a PR adds into a vhs recording, upload the gif to the qa-assets branch, and put a proof table in the PR's QA section. Scripts live in .claude/skills/messhall-tape-qa/scripts/.
Before you start
vhson PATH (brew install vhs, pulls ttyd and ffmpeg).- Run tapes from the worktree you are proving, with
pnpm dev <command>orpnpm messhall-dev <command>, so the recording shows the branch and not a globalmesshall. - A scratch messhall home, never the real data dir (
~/Library/Application Support/messhall). Every tape carriesEnv MESSHALL_HOME "/tmp/messhall-tape-home-<name>", and any tape that touches a daemon also its ownEnv MESSHALL_PORT, a free one from 7770 to 7799 (seedemo/tapes/README.md). No accounts, no login step.
1. Plan the shots
Read the PR's description (gh pr view <n> -R maximilianfalco/messhall --json body -q .body). Its "✅ QA and Testing" section and the feature map row's Verify command (.claude/skills/messhall-control/references/feature-map.md) list the cases. One tape per case: the command, the directory it runs in, any state it needs.
2. Take the shots
Tapes are code: demo/tapes/<slice>-<case>.tape, committed. Renders go to demo/out/, never committed. The rules are in demo/tapes/README.md:
- Keep the
Setblock (zsh, FontSize 18, Width 1400, Height 820, Padding 24, Catppuccin Mocha, TypingSpeed 40ms) so every recording looks the same. Outputbothdemo/out/<name>.gifand.mp4.Env MESSHALL_HOME "/tmp/messhall-tape-home-<name>", named after the tape.render.shreads this line, so it is required.- Open with
Hide/Type "clear"/Enter/Show. End with; echo exit $?on the command and aSleeplong enough to read the last frame. - A tape with claude seats gets its own
Env TMUX_TMPDIRandunset TMUXbefore any tmux command. A setTMUXbeatsTMUX_TMPDIR, so atmux kill-serverfrom inside a seat ends every real agent. By hand:env -u TMUX TMUX_TMPDIR=... tmux .... - Gifs must stay under 10MB for GitHub. For long takes,
Set Framerate 20or dropHeight.
Render from the directory the tape expects (the repo root or worktree unless it says otherwise):
bash .claude/skills/messhall-tape-qa/scripts/render.sh demo/tapes/<name>.tapeIt refuses to run unless vhs is on PATH and the tape's MESSHALL_HOME is set and is not the real data dir. Then it prints each output with its size. Pull the last frame (ffmpeg -sseof -0.3 -i demo/out/<name>.mp4 -frames:v 1 "$(mktemp -d)/last.png") and look at it before you upload.
Never record a key file, a real room transcript or anything from the real data dir.
3. Upload to GitHub
Push the gifs to the qa-assets branch from the repo:
pnpm -s messhall-dev qa-upload <pr> demo/out/<name>.gif ... >> urls.txtIt commits under pr-<n>/ with git plumbing (your branch and index stay as they are), pushes without force, and prints one  per file. build_qa.py reads those lines as they are. Never force-push qa-assets, it only grows.
4. Write the table
Back up the body first (gh pr view <n> -R maximilianfalco/messhall --json body -q .body > before.md). Then:
python3 .claude/skills/messhall-tape-qa/scripts/build_qa.py before.md rows.json urls.txt new.md
gh pr edit <n> -R maximilianfalco/messhall --body-file new.mdrows.json is [{"case": "...", "img": "<gif name without .gif>", "extras": ["exit 0", "all checks passed"]}]. img can be a list for side by side images, and width sets their size (720 by default). The script writes | case | recording | at the end of # ✅ QA and Testing (heading lines inside code blocks do not end the section), keeps the section's text, and replaces its own table on a rerun. A row with no url gets drag demo/out/<img>.gif here. It escapes < / > in extras and refuses em dashes.
--column screenshot writes a | case | screenshot | table for Mac app shots instead.
- Always pass
-R maximilianfalco/messhall. Acdinto the scratchpad makes plainghfail. - Write in the owner's voice: lowercase starts, plain words.
5. Check and hand off
Check the rendered body: gh api repos/maximilianfalco/messhall/issues/<n> -H 'Accept: application/vnd.github.full+json' --jq .body_html | grep -o '<img[^>]*>' shows each qa-assets src inside an <img>, not inside a code block. Report the rows, and any case with no recording and why.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

