Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

tui-testing

Estrellas2

Forks1

Actualizado7 de julio de 2026 a las 10:06

Run an interactive CLI/TUI app in tmux, send it input, and read its output. Use to test interactive apps.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

viktomas

viktomas/dotfiles

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	tui-testing
description	Run an interactive CLI/TUI app in tmux, send it input, and read its output. Use to test interactive apps.

Testing Interactive CLI Applications

Use a detached tmux session to drive any interactive app.

S=test  # session name

# start the app
tmux new-session -d -s "$S" -x 200 -y 50 'your-command --args'

# send input (text)
tmux send-keys -t "$S" 'hello world' Enter

# send special keys
tmux send-keys -t "$S" Escape
tmux send-keys -t "$S" C-c        # ctrl-c
tmux send-keys -t "$S" Down Down Enter

# read visible screen (add -e to keep ANSI colors)
tmux capture-pane -pt "$S"

# read full scrollback
tmux capture-pane -pt "$S" -S -

# kill the session when done
tmux kill-session -t "$S"

Notes

Give the app a moment to render before capturing: sleep 0.5 or poll.

To wait for a pattern:

until tmux capture-pane -pt "$S" | grep -q 'ready'; do sleep 0.3; done

The user can debug interactively: tmux attach -t "$S" (Ctrl+B then D to detach).
List/clean up: tmux ls, tmux kill-server.

Gotchas

A blank pane usually means "still initializing", not "crashed". Heavy TUIs can take many seconds to first paint (config/plugin/workspace scans). Poll the app's own log file for readiness instead of trusting a fixed sleep; a C-l redraw will not force a paint that hasn't happened yet.
Wrapped launches orphan the real process on kill-session. If you start the app through a shell wrapper (sh -c …, fish -c …, env … node …), tmux kill-session may reap only the wrapper and leave the actual child running — causing a second live instance, lock contention, or port conflicts on the next launch. After killing, confirm it's gone and pkill -f the command as a fallback:
```
tmux kill-session -t "$S" 2>/dev/null
pkill -f 'your-command --args' 2>/dev/null
```

Más de este repositorio

mismo repositorio

report

viktomas/dotfiles

Generate a standalone HTML report from a markdown file with d2 diagrams, SVGs, and syntax-highlighted code blocks. Use when the user asks for a report, a visual writeup, or a document with diagrams.

2026-07-082

gitlab-api

viktomas/dotfiles

Interact with GitLab REST API using GITLAB_TOKEN - use for TODOs, repositories, CI/pipelines, MRs, issues, and other API queries

2026-07-072

gdk

viktomas/dotfiles

GitLab Development Kit is a folder and set of utilities that contain most of the GitLab production systems. This skill is useful for testing with local GitLab deployment and when researching how feature works in the GitLab monolith, AIGW, workhorse and other services

2026-07-072

gitlab-api

viktomas/dotfiles

CRUD GitLab issues,MRs,pipelines,jobs,epics,issue comments

2026-07-072

projects

viktomas/dotfiles

my projects — gitlab namespace and ID, where they live on the local drive. Use whenever a question references a project by name, alias, or path, or when you need to locate a repo locally. Keywords - project, repo, where does X live, local path, gitlab-lsp, glab, cli, vscode extension, note, task, duo cli, dotfiles.

2026-07-072

review

viktomas/dotfiles

code changes review, use this skill any time I ask you to review a change

2026-07-072

name	tui-testing
description	Run an interactive CLI/TUI app in tmux, send it input, and read its output. Use to test interactive apps.

Testing Interactive CLI Applications

Use a detached tmux session to drive any interactive app.

S=test  # session name

# start the app
tmux new-session -d -s "$S" -x 200 -y 50 'your-command --args'

# send input (text)
tmux send-keys -t "$S" 'hello world' Enter

# send special keys
tmux send-keys -t "$S" Escape
tmux send-keys -t "$S" C-c        # ctrl-c
tmux send-keys -t "$S" Down Down Enter

# read visible screen (add -e to keep ANSI colors)
tmux capture-pane -pt "$S"

# read full scrollback
tmux capture-pane -pt "$S" -S -

# kill the session when done
tmux kill-session -t "$S"

Notes

Give the app a moment to render before capturing: sleep 0.5 or poll.

To wait for a pattern:

until tmux capture-pane -pt "$S" | grep -q 'ready'; do sleep 0.3; done

The user can debug interactively: tmux attach -t "$S" (Ctrl+B then D to detach).
List/clean up: tmux ls, tmux kill-server.

Gotchas

A blank pane usually means "still initializing", not "crashed". Heavy TUIs can take many seconds to first paint (config/plugin/workspace scans). Poll the app's own log file for readiness instead of trusting a fixed sleep; a C-l redraw will not force a paint that hasn't happened yet.
Wrapped launches orphan the real process on kill-session. If you start the app through a shell wrapper (sh -c …, fish -c …, env … node …), tmux kill-session may reap only the wrapper and leave the actual child running — causing a second live instance, lock contention, or port conflicts on the next launch. After killing, confirm it's gone and pkill -f the command as a fallback:
```
tmux kill-session -t "$S" 2>/dev/null
pkill -f 'your-command --args' 2>/dev/null
```