cli-verify

Automate interactive CLI and TUI testing in Ghostty windows with tmux and screenshot verification.

Updated Aug 23, 2026

Search Tags:#automation #testing #cli #tmux #ghostty #screenshot #terminal-ui

Ready to run

npx skills add https://github.com/nclandrei/dotfiles --skill cli-verify-nclandrei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cli-verify
Source: https://github.com/nclandrei/dotfiles/tree/main/config/skills/cli-verify
Command: npx skills add https://github.com/nclandrei/dotfiles --skill cli-verify-nclandrei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, swift, screencapture, open, git, and includes scripts (resource) components.

What problem does it solve?

Testing and debugging interactive CLI and TUI applications in realistic terminal environments becomes reliable with automated session management and visual verification.

Core Features & Use Cases

Isolated Ghostty-backed tmux sessions for safe concurrent testing across agents.
Built-in workflow to init, drive, capture, and cleanup a TUI session with a single script.
Supports screenshot-based validation and status reporting to verify UI behavior.

Quick Start

Run the helper to initialize a Ghostty-backed session and exercise your CLI app.

Frequently Asked Questions about cli-verify

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

FAQPage Schema

How do I test interactive CLI and TUI applications in a real terminal window?▼

You can test interactive CLI and TUI applications in a real Ghostty window by using tmux automation to initialize sessions, drive interactive input, capture screenshots, and verify UI behavior end-to-end.

Can I run concurrent terminal UI testing across multiple AI agents without session conflicts?▼

Yes, terminal UI testing supports concurrent execution across multiple AI agents by providing isolated Ghostty-backed tmux sessions, ensuring safe and conflict-free parallel testing environments.

How do I capture and verify terminal UI behavior with screenshots during automated testing?▼

Automated terminal UI testing captures screenshots within the Ghostty tmux session to validate visual output, verifying that interactive CLI elements render and behave correctly across different shells.

What dependencies do I need to automate terminal UI testing with Ghostty and tmux?▼

Automating terminal UI testing requires Ghostty, tmux, swift, git, and macOS screencapture tooling to manage sessions, drive input, and perform visual verification of CLI applications.

Does terminal UI testing work with both Codex and Claude agent contexts?▼

Yes, terminal UI testing adapts to both Codex and Claude environments, providing per-agent isolation so each context can independently initialize, drive, and verify its own Ghostty tmux sessions.

What is the best way to debug a TUI application that renders differently across multiple shells?▼

The best way to debug cross-shell TUI rendering issues is to run the application inside an isolated Ghostty tmux session, drive interactive input, and use screenshot validation to verify UI behavior across environments.