qa-tui

Automate black-box QA validation of terminal UI programs through a managed PTY.

1|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/laststance/skills --skill qa-tui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-tui
Source: https://github.com/laststance/skills/tree/main/skills/qa-tui
Command: npx skills add https://github.com/laststance/skills --skill qa-tui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terminal UI QA is complex and error-prone when manually validating behavior across surfaces, keybinds, and terminal states. This skill provides a structured, repeatable approach to automatically drive and evaluate TUI applications using a shell-driven PTY, ensuring consistent evidence collection and reporting.

Core Features & Use Cases

  • Shellwright-driven TUI testing: drive a TUI program within a managed PTY, capture raw bytes, screenshots, and session recordings.
  • Surface discovery & coverage: map main screens, modes, panes, and dialogs to ensure comprehensive validation.
  • Keybind evaluation & stability: exercise documented shortcuts to verify correct actions and clean exits across surfaces.
  • Evidence-driven QA reporting: generate a standardized report with health scoring and issue taxonomy, linking to captured evidence.

Quick Start

Launch a Shellwright-driven QA session against the target TUI by starting a PTY, recording, and systematically exercising surfaces and keybinds.

Frequently Asked Questions about qa-tui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate terminal UI testing without modifying the application source?

Automated TUI QA validates terminal interfaces by orchestrating phases like surface mapping, visual scans, keybind coverage, and exit behavior checks through a managed PTY. It systematically drives the application to produce a repeatable report with health scoring and issue taxonomy.

What's the best way to capture evidence like screenshots and recordings during TUI testing?

Capture TUI testing evidence by using a shell-driven PTY to record raw bytes, take screenshots, and save session recordings during validation. This evidence is linked directly into a standardized report with health scoring and issue taxonomy for traceable QA results.

How do I systematically cover keybinds and screen surfaces in terminal applications?

Cover keybinds and surfaces by first mapping main screens, modes, panes, and dialogs to ensure comprehensive validation. The process then exercises documented shortcuts across these discovered surfaces to verify correct actions and clean exits.

Can I test resize and exit behavior for terminal UI programs automatically?

Yes, you can test resize and exit behavior automatically by driving the TUI through a managed PTY. The QA validation scope explicitly includes checking how the terminal interface handles resizing and verifying clean exits across different application surfaces.

Does automated terminal UI testing require modifying the target application?

Automated terminal UI testing does not require modifying the target application. It operates as a black-box testing solution, driving the TUI program externally through a managed PTY to evaluate behavior and capture evidence without relying on source code changes.