@@ -11,6 +11,12 @@ can't reproduce, needs a design decision, too big for one focused change), the i
1111investigation note instead. A third party's linked PR ends it only when it survives a full review.
1212The skill lists the exact outcomes.
1313
14+ A note is where the work ends because it can't go further here, not where it hands the next step
15+ back. "The next step should be adding logs to the dispatcher" describes work you can still do on
16+ this runner, so it isn't an outcome: add the logs, run it, and report what they showed. Bail when
17+ you've concluded you can't fix the issue, and say why; don't bail while you can still make progress
18+ towards a fix.
19+
1420## Before you start an issue
1521
1622Read the whole thread with the GitHub MCP tools: the issue, every comment and its labels. The
@@ -196,7 +202,8 @@ miss. In short:
196202 substitute individual checks.
197203
198204- ** Root cause, not symptom.** Understand why it fails before changing code. A guard that hides the
199- failure is not a fix.
205+ failure is not a fix. When you don't understand it yet, instrument the code and run it here; a
206+ hypothesis in a note is not a result.
200207- ** The condensed repro becomes the regression test,** added to an existing test as described in
201208 [ Condense the repro into a test] ( #condense-the-repro-into-a-test ) . Watch it fail without the fix
202209 and pass with it; a test that never failed proves nothing. Check this again right before you
@@ -294,6 +301,14 @@ you ran, meaning the full matrix of browsers, versions and variations, not only
294301failed. That way the reader can trust the verdict without re-checking it. Call out any browser
295302divergence.
296303
304+ **No next steps you could take yourself.** A note that ends in "the next step would be to add
305+ logging to X", "someone should bisect this" or "worth checking whether Y" is unsatisfactory: that
306+ step is yours, and the runner is the place to take it. Add the logging, run the bisect, read the
307+ engine's source, try the variation, and come back with what it showed. Write the note only once you
308+ can't make progress any more: the repro needs something the runner doesn't have, the fix needs a
309+ design decision, the bug is in a browser, or every lead you had is exhausted. Then say what blocked
310+ you as a fact, with what you tried, not as a suggestion for someone else.
311+
297312**Voice.** The workflow posts the note as `github-actions`, so it speaks as the Playwright bot. Write
298313it as [bot-voice.md](bot-voice.md) says: announce the bot in one line, verdict first, everything
299314verbose in closed `<details>` blocks. The workflow appends a footer that names the bot and links the
0 commit comments