replay-debug

스타8

포크2

업데이트2026년 2월 28일 22:03

Replay and analyze Grove debug-record traces. Use when debugging runtime regressions, polling races, interactive input bugs, state transitions, frame/render mismatches, or when user asks to analyze `.grove/debug-record`. Not for instrumentation design, use `logging-best-practices` when adding or changing log events/fields. Trigger phrases: "replay", "debug record", "analyze trace", "runtime race", "timing bug", "state mismatch".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

MichaelVessia

MichaelVessia/grove

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Grove Replay Debug Skill

Use this skill when a bug report involves runtime behavior and timing.

If the task is adding/modifying logging events, switch to .agents/skills/logging-best-practices/SKILL.md.

Objective

Convert reported runtime issues into deterministic replay failures, fix against the failing sequence, and confirm replay passes on the same trace.

Inputs

Preferred: explicit trace path (for example .grove/debug-record-*.jsonl)
If missing: ask user to record one with cargo run -- --debug-record

Workflow

Locate trace:
- TRACE="$(ls -t .grove/debug-record-*.jsonl | head -n 1)"
Run strict replay first:
- cargo run -- replay "$TRACE"
If strict replay fails, note failing replay sequence from output.
Inspect nearby events:
- rg -n '"event":"replay"|"replay_seq"|\"seq\":<N>' "$TRACE"
If strict replay fails on frame hash and behavior may still be correct:
- cargo run -- replay "$TRACE" --invariant-only
For deeper diff context:
- cargo run -- replay "$TRACE" --snapshot .grove/replay-snapshot.json
Implement fix and rerun strict replay on same trace.
For regression inputs:
- cargo run -- replay "$TRACE" --emit-test <fixture-name>
- adds tests/fixtures/replay/<fixture-name>.jsonl

Reporting

When handing off, include:

Trace path used
Replay command(s) run
Failing sequence before fix (if any)
Replay result after fix
Any fixture emitted (tests/fixtures/replay/...)

Guardrails

Do not debug runtime issues from partial logs alone when replay trace is available.
Keep the original trace unchanged, copy via --emit-test for fixtures.
Prefer strict replay as source of truth, use --invariant-only only to isolate rendering-only drift.

이 저장소의 다른 Skills

같은 저장소

workspace-scale-benchmark

MichaelVessia/grove

Run and interpret Grove workspace scale performance benchmarks using `benchmark-scale`, including baseline capture, regression comparison, and optimization loops. Use when user asks about performance, scale, regressions, startup/discovery speed, polling/update throughput, p50/p95 timings, or benchmark harness usage. Trigger phrases: "benchmark-scale", "workspace scale", "perf regression", "p95", "performance baseline", "issue 38".

2026-03-028

logging-best-practices

MichaelVessia/grove

Instrumentation best practices for Grove's NDJSON event logging. Use when adding/changing log events, event fields, or logging schema in runtime code. Not for replay triage, use `replay-debug` for trace analysis and divergence debugging. Trigger phrases: "how to log", "add logging", "add event", "instrumentation", "telemetry", "event schema".

2026-02-288

frankentui

MichaelVessia/grove

Look up FrankenTUI framework APIs, patterns, and examples from the reference codebase at .reference/frankentui/. Use when asking about FrankenTUI APIs, widgets, layout, subscriptions, rendering, styling, hit testing, or any ftui-* crate. Trigger phrases: "frankentui", "ftui", "how does frankentui", "ftui widget", "ftui layout", "ftui subscription", "ftui runtime".

2026-02-148

name	replay-debug
description	Replay and analyze Grove debug-record traces. Use when debugging runtime regressions, polling races, interactive input bugs, state transitions, frame/render mismatches, or when user asks to analyze `.grove/debug-record`. Not for instrumentation design, use `logging-best-practices` when adding or changing log events/fields. Trigger phrases: "replay", "debug record", "analyze trace", "runtime race", "timing bug", "state mismatch".
allowed-tools	Read, Grep, Glob, Task

Grove Replay Debug Skill

Use this skill when a bug report involves runtime behavior and timing.

If the task is adding/modifying logging events, switch to .agents/skills/logging-best-practices/SKILL.md.

Objective

Convert reported runtime issues into deterministic replay failures, fix against the failing sequence, and confirm replay passes on the same trace.

Inputs

Preferred: explicit trace path (for example .grove/debug-record-*.jsonl)
If missing: ask user to record one with cargo run -- --debug-record

Workflow

Locate trace:
- TRACE="$(ls -t .grove/debug-record-*.jsonl | head -n 1)"
Run strict replay first:
- cargo run -- replay "$TRACE"
If strict replay fails, note failing replay sequence from output.
Inspect nearby events:
- rg -n '"event":"replay"|"replay_seq"|\"seq\":<N>' "$TRACE"
If strict replay fails on frame hash and behavior may still be correct:
- cargo run -- replay "$TRACE" --invariant-only
For deeper diff context:
- cargo run -- replay "$TRACE" --snapshot .grove/replay-snapshot.json
Implement fix and rerun strict replay on same trace.
For regression inputs:
- cargo run -- replay "$TRACE" --emit-test <fixture-name>
- adds tests/fixtures/replay/<fixture-name>.jsonl

Reporting

When handing off, include:

Trace path used
Replay command(s) run
Failing sequence before fix (if any)
Replay result after fix
Any fixture emitted (tests/fixtures/replay/...)

Guardrails

Do not debug runtime issues from partial logs alone when replay trace is available.
Keep the original trace unchanged, copy via --emit-test for fixtures.
Prefer strict replay as source of truth, use --invariant-only only to isolate rendering-only drift.