tmux-cli-test
/tmux-cli-test
Test interactive CLI and TUI behavior in a terminal using tmux. Use for keyboard navigation, prompts, redraws, or terminal-dependent behavior; ordinary command output and exit-code checks can run directly.
Assessment and security
- Files in this package
- 3
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/tmux_docker_helpers.sh, scripts/tmux_helpers.sh
What it does and when to use it
Test interactive CLI and TUI behavior in a terminal using tmux. Use for keyboard navigation, prompts, redraws, or terminal-dependent behavior; ordinary command output and exit-code checks can run directly.
Original author description
Test interactive CLI and TUI behavior in a terminal using tmux. Use for keyboard navigation, prompts, redraws, or terminal-dependent behavior; ordinary command output and exit-code checks can run directly.
How it works
- Helpers
SKILL.md preview
--- name: tmux-cli-test description: Test interactive CLI and TUI behavior in a terminal using tmux. Use for keyboard navigation, prompts, redraws, or terminal-dependent behavior; ordinary command output and exit-code checks can run directly. --- # Test terminal interactions Use a tmux session to exercise the requested behavior and capture evidence. Choose scenarios for the change: readiness, input, navigation, cancellation, resize, or error recovery as relevant. Use disposable data for actions that modify state. ## Helpers The optional [Bash helpers](scripts/tmux_helpers.sh) provide bounded condition waits, input, assertions, and captures. They require `tmux` and `bc`, and sourcing them enables `set -euo pipefail`. Source them in a dedicated Bash invocation. `tmux_start` kills a same-named session first, so choose a unique session name and clean up only sessions created for this test. For example, from the repo root: ```bash source .claude/skills/tmux-cli-test/scripts/tmux_helpers.sh session="vz-cli-test-$$" trap 'tmux_kill "$session"' EXIT tmux_start "$session" "env PS1='cli-test> ' bash --noprofile --norc -i" tmux_wait_for "$session" "cli-test>" 10 tmux_type "$session" "printf '%s%s\\n' terminal- ready" tmux_send "$session" Enter tmux_wait_for "$session" "terminal-ready" 10 tmux_capture "$session" ``` Replace the shell and expected text with the application and observable state being tested. Prefer a bounded wait for an expected state over a fixed delay. A timeout should retain a frame/log for diagnosis. | Helper | Use | | --- | --- | | `tmux_send <session> <keys...>` | Special keys such as Enter, Escape, C-c | | `tmux_type <session> <text>` | Literal input | | `tmux_wait_for <session> <text> [seconds]` | Wait for visible text | | `tmux_wait_for_regex <session> <regex> [seconds]` | Wait for an extended regex | | `tmux_wait_gone <session> <text> [seconds]` | Wait for text to disappear | | `tmux_capture <session>` / `tmux_capture_ansi <session>` | Capture plain/ANSI text | | `tmux_assert_contains <session> <text>` | Check current pane text | A visible input echo does not prove an action succeeded. Assert the resulting application state. Session disappearance alone does not prove a zero exit code; use process/log evidence when exit status matters. For an already selected Docker test environment, the optional [Docker helpers](scripts/tmux_docker_helpers.sh) target an existing session via `TMUX_DOCKER_CONTAINER` and `TMUX_DOCKER_SESSION`. They use the active Docker connection; confirm that it is the intended Machine/container. Do not substitute a global daemon for a vz Machine's private Docker. Report the command, interactions, observed result, and evidence. Text captures support content assertions; color/layout claims require inspecting the actual rendering. Broader backend certification still follows AGENTS.md.
Files in this package (3)
- SKILL.md 3 KB
- scripts/tmux_docker_helpers.sh 6 KB
- scripts/tmux_helpers.sh 13 KB
Versions
The database has no other skills named tmux-cli-test.
Database snapshot: 13.11.2026 · package version 3a2db193acd5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100terminal-emulator
Test interactive CLI/TUI applications using @microsoft/tui-test. Use when you need to test CLI tools with interactive prompts, TUI rendering, arrow key navigation, or any command that requires a TTY. Triggers include "test CLI", "test TUI", "run interactively", "automate… - 96tmux
Use when a CLI task needs an interactive terminal or control of a tmux session. - 100tmux-automation
Drive CLI tests inside isolated tmux/byobu sessions with ai-monitor integration. Use when asked to "test this CLI", "run it in tmux", "automate a terminal session", "capture the output of an interactive command", "send keystrokes to a session", or to exercise a plugin or… - 100tmux-real-user-testing
This skill should be used when the user asks to "用 tmux 做真实测试", "保存 tmux 日志", "像真实用户一样测试 Qwen", "生成可复查的 TUI 测试报告", "测试 slash command 交互", or requests a tmux-based real user E2E run with complete readable logs. It guides real TUI usage with step-by-step capture-pane snapshots… - 100terminal-ui
Terminal User Interface (TUI) performance and UX guidelines for TypeScript applications using Ink and Clack. This skill should be used when building CLI tools, interactive terminal prompts, or developer tooling with TUI components. Triggers on tasks involving TUI components, CLI… - 100qa
QA a change in the running program, the way its user meets it: drive a CLI or terminal UI through tmux, a web app through a browser, and check every requested behavior against what you observe. Use after implementing a change and before code review, or when the user asks for a…