tmux-qa
/tmux-qa
Sprawdza zmiany przez budowanie, testy i uruchomienie aplikacji w tmux, aby potwierdzić działanie od początku do końca.
- Autor
- kylesnowschwartz ↗
- Repozytorium
- ralph-ban ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 24.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.08.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/tmux-wrapper.sh
Co robi i kiedy
Sprawdza zmiany przez budowanie, testy i uruchomienie aplikacji w tmux, aby potwierdzić działanie od początku do końca.
Wyzwalacze z opisu
Argumenty
/tmux-qa [scope of changes to verify]
Oryginalny opis (EN)
This skill should be used when the user asks to "QA changes", "verify this works", "test the build", "check if this runs", "validate changes in tmux", or wants end-to-end verification of code changes by running builds, tests, and applications in tmux.
Jak działa
- Bundled Resources
- Workflow
- tmux Primitives
- Rules
- Report Format
Podgląd SKILL.md
---
name: tmux-qa
description: This skill should be used when the user asks to "QA changes", "verify this works", "test the build", "check if this runs", "validate changes in tmux", or wants end-to-end verification of code changes by running builds, tests, and applications in tmux.
argument-hint: "[scope of changes to verify]"
---
# tmux-QA
Drive an isolated tmux session: build, run, observe, report.
**Scope**: $ARGUMENTS
If no scope was provided, read the recent changeset to determine what needs verification.
## Bundled Resources
- `references/tmux-primitives.md` — deeper tmux primer (key names, working-directory tricks, common patterns for vim/REPL/git rebase, common mistakes). Load when verifying interactive tools or when the inlined Primitives section below is insufficient.
- `scripts/tmux-wrapper.sh` — optional helper that collapses `new-session` / `send-keys` / `capture-pane` / `kill-session` into single commands. See the reference file for usage. Raw `tmux` commands work just as well.
## Workflow
1. Read the changeset — `git diff`, `git log`, understand what changed
2. Detect the project — look for `Makefile`, `go.mod`, `package.json`, `Cargo.toml`, etc. Read `README` and `CLAUDE.md` for build instructions
3. Create an isolated tmux session — never touch the user's existing sessions
4. Build and test — run the project's build and test commands in the isolated session
5. Run the thing — for servers, CLIs, and TUIs, actually run them and verify behavior
6. Verify specific changes — if the diff adds an endpoint, test it. If it fixes a bug, confirm the fix
7. Clean up — kill the test session
8. Report — structured PASS / FAIL / PARTIAL with evidence
## tmux Primitives
### Session lifecycle
Create an isolated session with a unique name and guarantee teardown:
```bash
TEST_SESSION="qa-$(date +%s)"
# Default geometry is fine for CLIs and servers
tmux new-session -d -s "$TEST_SESSION"
# For TUIs, pin dimensions so layout is deterministic
tmux new-session -d -s "$TEST_SESSION" -x 120 -y 40
# Guarantee teardown even if the script errors partway through
trap 'tmux kill-session -t "$TEST_SESSION" 2>/dev/null' EXIT
```
### Running commands
Send commands with a distinctive exit sentinel so assertions don't false-match on program output:
```bash
tmux send-keys -t "$TEST_SESSION" 'go build ./... 2>&1; echo "__QA_EXIT__:$?"' Enter
# Special keys for TUIs
tmux send-keys -t "$TEST_SESSION" C-c # interrupt
tmux send-keys -t "$TEST_SESSION" Escape # ESC
tmux send-keys -t "$TEST_SESSION" C-o # ctrl+o
tmux send-keys -t "$TEST_SESSION" Up Down Tab # arrows, tab, etc.
```
The sentinel reflects only the *foreground* command's exit. It does not survive `cmd &`, `nohup`, daemonisers, or fork-and-return wrappers — in those cases wait on a different signal (a log line via `log-tail-qa`, a port becoming reachable, a DB row appearing).
For multi-line input where each line should be typed (REPLs and editors distinguish typing from paste), send keys per line:
```bash
tmux send-keys -t "$TEST_SESSION" 'first line' Enter
tmux send-keys -t "$TEST_SESSION" 'second line' Enter
```
Embedded newlines in a single `send-keys` can trigger bracketed-paste handling, which is not the same as typing. For specs that assert behaviour only observable when typed (autocomplete, debounced highlighting), key-by-key is correct.
### Reading output (the assertion primitive)
```bash
# Current visible content
tmux capture-pane -t "$TEST_SESSION" -p
# With scrollback (long builds overflow the default view)
tmux capture-pane -t "$TEST_SESSION" -p -S -200
# Both alternate-screen and main-screen — required for vim, less, htop, full-screen TUIs
tmux capture-pane -t "$TEST_SESSION" -p -a
```
`capture-pane` includes the echoed command. Assertions must match patterns that appear only in the *output*, not the invocation.
**Alternate-screen trap.** `vim`, `less`, `htop`, and most full-screen TUIs switch to an alternate screen on start. Without `-a`, alt-screen content is gone once the program exits. Capture *during* the asserted state, not after.
**`TERM` divergence.** Default `TERM` inside tmux is `screen` or `tmux-256color`. Some TUIs refuse colour or alt-screen modes against unrecognised values. Set `default-terminal` in tmux or `TERM=xterm-256color` for the asserted command if the capture shows no colour.
### Waiting for output
Poll `capture-pane`; do not sleep-and-hope:
```bash
for i in $(seq 1 30); do
if tmux capture-pane -t "$TEST_SESSION" -p | grep -q "__QA_EXIT__:0"; then
break
fi
sleep 0.5
done
```
### Multiple panes
Target panes explicitly once split, using `session:window.pane`:
```bash
# Split for parallel work (server + client pattern)
tmux split-window -h -t "$TEST_SESSION"
tmux send-keys -t "$TEST_SESSION:0.0" 'make run' Enter
# poll pane 0 for "listening on" or similar ready signal...
tmux send-keys -t "$TEST_SESSION:0.1" 'curl -sf localhost:8080/health' Enter
```
## Rules
- **Own session only.** Create `qa-<timestamp>`, never operate in existing sessions.
- **Always clean up.** Kill the session when done, even on failure. Prefer `trap … EXIT` over hoping execution reaches the teardown line.
- **Pin geometry for TUIs.** Pass `-x W -y H` to `new-session` when layout depends on terminal size; otherwise the default is fine.
- **Read before asserting.** Use `capture-pane`; do not assume.
- **Use a distinctive exit sentinel.** Append `; echo "__QA_EXIT__:$?"` so assertions don't collide with normal program output.
- **Poll, don't race.** Builds and servers take time. Check `capture-pane` in a loop.
- **Report evidence.** Show actual output for failures. "Build failed" is useless — show the error.
- **Stay in scope.** Verify what changed, unless asked for a full regression.
## Report Format
```
## QA Report
**Scope**: <what was verified>
**Verdict**: PASS | FAIL | PARTIAL
### Build
- [PASS/FAIL] `<command>` -- <notes>
### Tests
- [PASS/FAIL] `<command>` -- <N passed, M failed>
- <failure details if any>
### Runtime Verification
- [PASS/FAIL] <what was checked> -- <evidence>
### Issues
1. <description with actual output>
```
Pliki w paczce (3)
- SKILL.md 6 KB
- references/tmux-primitives.md 6 KB
- scripts/tmux-wrapper.sh 2 KB
Wersje
W bazie nie ma innych skilli o nazwie tmux-qa.
Migawka bazy z 13.11.2026 · wersja paczki 56fa52bed3c4 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95tmux-start
Startuje pracę nad zgłoszeniem w nowym oknie tmux z osobnym worktree, gdy użytkownik działa w sesji tmux. - 96tmux
Steruje sesją tmux i interaktywnym terminalem, gdy zadanie w linii poleceń wymaga stałego okna. - 100tmux-icons
Zmienia motywy ikon w pasku stanu tmux dla wtyczki claude-tmux-status lub dostosowuje pojedyncze ikony. - 100tmux-real-user-testing
Przeprowadza testy TUI jak prawdziwy użytkownik w tmux, zapisując zrzuty ekranu i pełny log do późniejszego sprawdzenia. - 100smux
Steruje panelami tmux i komunikuje się między agentami, czytając inne panele i wysyłając wiadomości. - 100workmux
Zarządza agentami terminalowymi, git worktree i sesjami tmux przez workmux: otwiera agentów w projekcie, sprawdza ich postęp i obsługuje równoległe przepływy agentów.