rembric-tui-installer-e2e

What problem does it solve?

This Skill solves the risk of shipping broken Rembric TUI installer updates that disrupt user setup workflows, and eliminates the hassle of testing installer UI/UX changes in a way that pollutes your local development environment with test configs, plugins, or running server instances.

Core Features & Use Cases

• Layered CI-safe validation: Run headless syntax checks and automated test suites in continuous integration pipelines to catch regressions like broken shell syntax, failed plugin installs, or incorrect token generation before code is merged.
• Full install workflow testing: Validate end-to-end install and uninstall round-trips for supported AI coding agents, test TUI navigation and screen rendering in a real terminal, and run full Docker smoke tests to confirm the Rembric server starts correctly and health endpoints respond as expected.
• Isolated UX iteration: Test installer UI/UX changes in a disposable temporary environment that never touches your real home directory, agent configuration folders, or running services, making it safe to demo or refine the installer's look and feel without risk.
• Use Case: A developer modifying the installer's shell scripts, UI layout, or distribution documentation can run this Skill to catch bugs early in the development cycle, and test visual or interaction tweaks in the sandbox without disrupting their local setup.

Quick Start

Use this skill to run full end-to-end validation of the Rembric TUI installer before merging any changes to its code or documentation, and use the provided sandbox script to manually test and refine the installer's UI/UX in isolation when making visual or interaction updates.