tui-validation-loop-automation

Run the live TUI validation workflow from test/ and record issues in ISSUES.md.

5|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/lhy0718/AutoLabOS --skill tui-validation-loop-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-validation-loop-automation
Source: https://github.com/lhy0718/AutoLabOS/tree/main/.codex/skills/tui-validation-loop-automation
Command: npx skills add https://github.com/lhy0718/AutoLabOS --skill tui-validation-loop-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce and validate real TUI defects by running the repository's own test/ workflow in a live session, enabling issue discovery and governance without relying on mocked substitutes.

Core Features & Use Cases

  • Reproduce a live TUI issue from test/ in a fresh session to observe authentic behavior.
  • Record context, steps, and outcomes in ISSUES.md with structured guidance.
  • Apply the smallest plausible fix, then re-run the same flow to verify stability and check nearby regressions.
  • Maintain governance by keeping live validation tied to node-owned execution and revalidation cycles.

Quick Start

Run the live TUI validation loop from test/, record the issue in ISSUES.md, apply the smallest fix, and revalidate the flow.

Frequently Asked Questions about tui-validation-loop-automation

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

FAQPage Schema
How do I reproduce a live TUI defect from a test workflow?

Run the repository's real validation workflow from the test/ directory in a fresh session to reproduce a live TUI defect. This observes authentic behavior without relying on mocked substitutes, capturing the exact conditions that triggered the issue.

What is the best way to track and document TUI issues discovered during a live run?

Record each observed TUI issue in ISSUES.md during the live run. Document the context, reproduction steps, and expected versus actual outcomes to maintain structured governance over the validation cycle and ensure traceability.

How do I apply a patch to fix a TUI defect and check for regressions?

Patch the smallest plausible root cause of the TUI defect, update the corresponding tests under tests/, and re-run the same validation flow. This confirms the fix while actively checking for nearby regressions in the live session.

Does TUI validation require mocked environments or test substitutes?

TUI validation does not require mocked substitutes. It reproduces and validates real defects by running the repository's own test/ workflow in a live session, enabling authentic issue discovery and governance.

Why should I use a live validation loop instead of standard automated tests for TUI defects?

A live validation loop ties execution to node-owned cycles and revalidation, ensuring that TUI defect fixes are confirmed against authentic behavior rather than mocked conditions, which standard automated tests may fail to capture.