control-cli

Drive interactive CLI or TUI sessions in isolated tmux or PTY environments.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill control-cli-nthpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: control-cli
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/plugins/cache/cursor-public/cursor-team-kit/d1cdb88a9eb33cf392395c87e3fd76419fc1010e/skills/control-cli
Command: npx skills add https://github.com/nthpaul/dotfiles --skill control-cli-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building confidence in an interactive CLI or TUI is hard because manual testing misses edge cases like prompts, interrupts, resize behavior, and startup regressions, and it’s difficult to reproduce failures reliably.

Core Features & Use Cases

  • Deterministic harness workflow: Reuses existing repo test/demo harnesses when available or builds a temporary harness that drives the CLI in an isolated session.
  • Interactive flow coverage: Exercises keyboard-driven flows step-by-step (text, Enter, arrows, Escape, Ctrl-C, and terminal resizes) while capturing transcripts for comparisons.
  • Profiling and regression triage: Supports startup timing checks, CPU profiling, heap/memory leak investigation, and hang diagnosis by capturing before/after artifacts.

Quick Start

Use the control-cli harness to run the specific command under test in an isolated tmux or PTY session and capture a transcript while you drive the interactive prompts and flows.

Frequently Asked Questions about control-cli

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

FAQPage Schema
How do I test interactive CLI prompts and TUI flows deterministically?

Interactive CLI testing requires driving keyboard inputs like Enter, arrows, and Escape within an isolated tmux or PTY session while capturing terminal transcripts for reliable stepwise prompt-flow verification.

How can I profile CLI startup timing and diagnose hangs in a terminal application?

CLI profiling involves running the command in an isolated harness to capture before and after artifacts, enabling startup timing checks, CPU profiling, and memory leak investigation for hang diagnosis.

Can I automate terminal resize and interrupt behavior testing for a TUI?

Terminal resize and interrupt behavior testing applies deterministic harnesses to simulate window size changes and Ctrl-C signals in a PTY session, capturing screen synchronization artifacts for comparison.

What is the best way to capture a reproducible terminal transcript for CLI regression testing?

Terminal transcript capture uses a temporary harness to execute the CLI in an isolated environment, driving interactive flows stepwise and recording screen outputs to create reproducible regression testing artifacts.

Does CLI testing with tmux require external services or complex dependencies?

CLI testing with tmux requires no external services, relying instead on a reproducible minimal workspace and isolated local execution via PTY probing to ensure clean session cleanup.