Assert regex patterns in log streams within bounded timeouts.
npx skills add https://github.com/kylesnowschwartz/ralph-ban --skill log-tail-qa
Please help me install this Agent Skill. Skill: log-tail-qa Source: https://github.com/kylesnowschwartz/ralph-ban/tree/main/skills/log-tail-qa Command: npx skills add https://github.com/kylesnowschwartz/ralph-ban --skill log-tail-qa
Verifying that an asynchronous system actually emitted a specific log line (and doing so reliably) is hard, because the log may already contain historical entries, may buffer output, may rotate, or may stop growing without the expected event.
Use the log-tail-qa skill to verify that a regex pattern appears in the target log within a bounded time window and capture the matching lines plus tail context for audit evidence.
High-intent search queries and answers about installing and using this skill.
To verify log line appearance within a bounded time, you can tail a log file with a configurable timeout, asserting a regex pattern matches deterministically instead of waiting forever. This captures matched lines and tail context for an auditable verdict.
Testing asynchronous CLI behavior using log output involves asserting that a streamed log source contains a regex pattern within a bounded time window. This applies oracle-driven TUI and CLI verification scenarios where card state transitions depend on log emission.
To detect if a log file stops growing during asynchronous testing, you can use a no-progress fail-fast mechanism that polls the log across intervals. It rejects early and fails deterministically when the system appears stuck or writes elsewhere.
Yes, you can assert that a regex pattern matches exactly N times in a log file by using line-based accumulation for occurrence counting. This supports asserting N matches rather than relying on first-match-only grep patterns.
Log tail verification works with container streams, captured stdout/stderr, file tails, and journal streams. It handles history-vs-tail semantics to correctly match entries that already happened or must happen after verification starts.
To save matched log lines and context for an auditable test verdict, you can capture evidence into an oracle evidence directory. This persists matched lines, surrounding context, and verdict details for later review.
yun520-1Parse and search application logs using grep, awk, jq, and Python3.
coltonbattsSearch and analyze JSONL conversation logs using jq and rg.
clawperatorProcesses and tests mixed stdout and stderr streams from CLI commands.
oracle-devrelSend keystrokes and scrape pane output from tmux sessions.
