e2e-test-debug-loop

Automate GUI end-to-end tests via X11 keystrokes with structured reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/brian-wijaya/dotfiles --skill e2e-test-debug-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test-debug-loop
Source: https://github.com/brian-wijaya/dotfiles/tree/main/.claude/skills/e2e-test-debug-loop
Command: npx skills add https://github.com/brian-wijaya/dotfiles --skill e2e-test-debug-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end testing by simulating human GUI input via X11 keystrokes and mouse events, enabling reliable validation of interactive software without manual testing handoffs.

Core Features & Use Cases

  • End-to-end validation of features in GUI applications using human-like input sequences.
  • Automated test orchestration with retry loops and structured reporting, including screenshots and diffs.
  • Use cases include regression testing after deployments, acceptance testing for new builds, and QA demos for stakeholders.

Quick Start

Invoke the skill with a story file or feature name to start a test session and generate a comprehensive report.

Frequently Asked Questions about e2e-test-debug-loop

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

FAQPage Schema
How do I automate E2E testing with human-like GUI input in X11?

You can automate E2E testing by emulating human GUI input through X11 keystrokes, typing, and mouse clicks, then validating outcomes with somatic QA and generating structured test reports with baseline captures and diffs.

Can I use X11 keystrokes and mouse events for automated regression testing after deployments?

Yes, X11 keystrokes and mouse events support automated regression testing after deployments by orchestrating test sessions with retry loops, capturing baseline and result screenshots, and persisting test results in a vault.

What is the best way to generate structured test reports for GUI automation?

The best way to generate structured test reports for GUI automation is to orchestrate X11 input sequences, capture baseline and result screenshots, apply somatic QA validation, and persist structured reports in a vault.

Does E2E test automation work with X11 for acceptance testing in GUI environments?

Yes, E2E test automation works with X11 for acceptance testing in GUI environments by using x11_key, x11_type, and x11_click actions to simulate human input, validate new builds, and generate comprehensive acceptance reports.

Why do I need a vault for E2E test orchestration and result persistence?

You need a vault for E2E test orchestration to persist test results, baseline captures, and diffs, ensuring structured reports remain accessible for regression testing, deployment verification, and stakeholder QA demos across sessions.

What are the limitations of using X11 emulation for end-to-end testing?

X11 emulation for E2E testing is limited to GUI environments supporting X11 keystrokes and mouse events, requiring x11_key, x11_type, and x11_click actions, making it unsuitable for headless environments without an X11 display server.