tmux-tdd

Monitor tmux pane test output to drive the RED-GREEN-REFACTOR workflow.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/ianphil/my-skills --skill tmux-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux-tdd
Source: https://github.com/ianphil/my-skills/tree/main/tmux-tdd
Command: npx skills add https://github.com/ianphil/my-skills --skill tmux-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reading test output and coordinating actions across tmux panes can be error-prone and tedious in a multi-language project. This skill provides a consistent, pane-driven approach to observe test progress, detect failures, and drive the TDD cycle without leaving the terminal.

Core Features & Use Cases

  • Read and parse test results directly from tmux panes across languages (Rust, Python, JavaScript, Go, and more).
  • Orchestrate the RED-GREEN-REFACTOR workflow by coordinating actions between a code pane and a test runner pane.
  • Works with any language in a split-pane workflow and supports common test runners (cargo test, pytest, jest/vitest, go test).
  • Use case: in a fast-paced development session, automatically advance to the next step when tests pass, or pause and debug when failures occur.

Quick Start

Open a tmux session with a code pane and a test-runner pane, then activate tmux-tdd to start monitoring test output and orchestrating the workflow.

Frequently Asked Questions about tmux-tdd

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

FAQPage Schema
How do I automate test-driven development in a tmux split-pane workflow?

Automating test-driven development in a tmux split-pane workflow involves monitoring test output from a test runner pane to drive the RED-GREEN-REFACTOR cycle. This skill parses standard pass/fail patterns to coordinate pane actions and advance the workflow automatically when tests pass.

Can I parse test output from multiple languages like Rust, Python, and Go in tmux?

Yes, you can parse test output from multiple languages in tmux. This skill recognizes standard pass/fail patterns from common test runners including cargo test, pytest, jest, vitest, and go test, enabling consistent test monitoring across different programming languages.

How does tmux-tdd orchestrate the RED-GREEN-REFACTOR TDD cycle?

tmux-tdd orchestrates the RED-GREEN-REFACTOR cycle by monitoring and interpreting test output from tmux panes. It detects test failures to pause for debugging and automatically advances to the next workflow step when tests pass, coordinating actions between code and test runner panes.

What do I need to set up before using pane-based TDD orchestration in tmux?

To use pane-based TDD orchestration in tmux, you need a tmux session configured with at least a code pane and a test-runner pane. You also need common test runners installed for your project's language, such as cargo test, pytest, jest, or go test.

Does this TDD workflow support test runners like jest and vitest?

Yes, this TDD workflow supports test runners like jest and vitest. It works with common test runners across multiple languages, including cargo test for Rust, pytest for Python, and go test for Go, recognizing their standard output patterns to detect pass or fail states.

Why should I use tmux panes for test-driven development instead of switching windows?

Using tmux panes for test-driven development prevents error-prone and tedious window switching by keeping code and test output visible simultaneously. It provides a consistent, pane-driven approach to observe test progress, detect failures, and drive the TDD cycle without leaving the terminal.