Verifying changes in a terminal user interface is easy with these simple steps. You can start and use Codex TUI interactively to check everything works.
Always set RUST_LOG to trace when starting the process. Pass a log directory argument to have logs written to a specific folder. This helps with debugging.
When sending a test message, send the text first. Then send Enter in a separate write. Do not send text and Enter together. Use the just codex command to run the tool.
Global
mkdir -p ~/.claude/skills/test-tuiProject
mkdir -p .claude/skills/test-tuiSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step