run-and-watch

Track command execution against X11 events and timing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracks a command's execution against X11 events and timing to help understand side effects and GUI interactions.

Core Features & Use Cases

  • Observes command execution alongside X11 events such as CreateNotify, MapNotify, and DestroyNotify.
  • Records precise start and end times and reports duration and anomalies.
  • Use Case: Debug a script that opens a new window and verify expected event sequence during automation.

Quick Start

Use the skill by supplying the command to observe as ARGUMENTS. Example: ls -la /tmp

Frequently Asked Questions about run-and-watch

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

FAQPage Schema
How do I track X11 events while running a command for GUI debugging?

Track X11 events by running your command while observing CreateNotify, MapNotify, and DestroyNotify signals. This records start and end times, measures duration, and reports anomalies to help debug GUI workflows and desktop applications.

What is the best way to diagnose window lifecycle issues during desktop automation?

Diagnose window lifecycle issues by capturing X11 events against command execution timing. This verifies expected event sequences, such as MapNotify and DestroyNotify, to pinpoint focus or window creation anomalies during automation scripts.

Can I measure command execution duration alongside GUI interactions in X11?

Measure command execution duration alongside GUI interactions by marking start time, running the command, and capturing X11 events. This produces a structured report detailing elapsed time and any detected GUI side effects.

How do I verify expected X11 event sequences when testing desktop applications?

Verify expected X11 event sequences by running the target application command and observing captured events. The tool marks the start time, runs the command, and generates a structured report of the event flow.

Do I need X11 tooling to observe command execution side effects?

X11 tooling is required to observe command execution side effects. The tool uses Somatic temporal and X11 components to capture CreateNotify, MapNotify, and DestroyNotify events while tracking execution timing.

Why does my GUI automation script open a window at the wrong time?

GUI automation scripts open windows at the wrong time due to unexpected event sequences. Track X11 events like MapNotify against precise timing to identify where the window lifecycle deviates from expected behavior.