Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, actionable reference for rr-based debugging with clear command coverage for both regular and ASAN crashes and a bundled automation script. Weak spots are the thin automation-script pointer and the absence of a worked script invocation.
Suggestions
Expand the 'Automation Script' section with a concrete invocation example, e.g. `python scripts/crash_trace.py --steps 100 --asan <trace-dir>`, and list its key flags.
Replace the 'next\nnext\n...' placeholder in both crash-extraction sections with an explicit instruction like 'repeat `next` until you reach the crashing instruction' to avoid ambiguity.
De-duplicate the repeated 'rr replay' line across the crash-extraction sections by referencing the Core Workflow once.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with terse command listings and no padding about what gdb/rr is, but the two crash-extraction sections lightly repeat 'rr replay' and the 'next/next/...' pattern, leaving minor trimming opportunities. | 4 / 5 |
Actionability | Concrete executable gdb commands ('rr record <program> [args]', 'reverse-next 100', 'break *$pc', 'x/10xb <addr>') cover regular and ASAN cases, but the bundled script has no worked invocation example and 'next\n...' is a placeholder pattern. | 4 / 5 |
Workflow Clarity | Core record→replay sequence and the regular/ASAN extraction sub-workflows are clearly sequenced; these are read-only inspection flows so no validation checkpoint is required, though no explicit error-recovery loop is given. | 4 / 5 |
Progressive Disclosure | Well-organized section headers with one real one-level-deep reference (scripts/crash_trace.py, verified present), but the automation pointer is a bare sentence without usage/args, leaving a minor signaling gap. | 4 / 5 |
Total | 16 / 20 Passed |