terminal-capture

You can automate terminal UI screenshot testing by executing CLI commands in a pseudo-terminal and capturing the output visually. This skill uses Playwright and node-pty to render terminal interactions, generating screenshots for visual regression testing and documentation.

Visual regression testing for terminal output captures CLI command results as images to detect unintended UI changes. You need it when reviewing pull requests that modify slash commands or terminal interactions, ensuring visual consistency across updates.

Yes, you need npm and Playwright browser installation to capture terminal screenshots. The automation relies on node-pty to simulate the terminal environment and Playwright to capture the visual output of the executed CLI commands.

Yes, you can generate visual documentation for slash commands using terminal automation. By running the target commands through the capture process, the skill automatically produces screenshot visual aids that document the exact terminal interactions and output.

The best way to verify CLI output changes in a pull request is to use automated screenshot capturing. This skill executes the modified CLI commands and generates visual screenshots, allowing you to compare the terminal output before and after the code changes.

Terminal screenshot testing requires a pseudo-terminal because standard output capture misses visual formatting. Using node-pty ensures the CLI commands run in an interactive environment, allowing Playwright to accurately capture colors, layouts, and dynamic terminal UI elements.