From 790d899d2661f33f20bcd696fba5cb3f687534b3 Mon Sep 17 00:00:00 2001 From: veko Date: Thu, 10 Sep 2026 19:48:16 +0800 Subject: [PATCH] pstack: bug-fix playbook gets a flake-triage rule A test that failed once is a bug until proven otherwise. Capture the assertion before any rerun, treat fails-in-suite / passes-alone as shared state, and require a reproduction or tracker entry before calling it a flake. Privacy and security assertions never get the flake label. Co-authored-by: Cursor --- pstack/skills/poteto-mode/playbooks/bug-fix.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pstack/skills/poteto-mode/playbooks/bug-fix.md b/pstack/skills/poteto-mode/playbooks/bug-fix.md index 88307807e..dd4ffe0b9 100644 --- a/pstack/skills/poteto-mode/playbooks/bug-fix.md +++ b/pstack/skills/poteto-mode/playbooks/bug-fix.md @@ -14,4 +14,6 @@ Be scientific. Every shipped line traces to runtime evidence. Belt-and-suspender Investigation fans out `how` + `why` as parallel subagents. +A test that failed once is a bug until proven otherwise. Capture the full failure output before rerunning. A rerun without a saved assertion destroys the evidence. Fails-in-suite but passes-alone is the signature of order-dependent shared state, not noise. Name the shared resource before you stop. A flake verdict needs a captured assertion plus either a reproduction or a tracker entry. One green rerun earns neither, and a privacy or security assertion never earns it at all. + **Reply:** what was broken, root cause, fix, how you verified. Paste failing-then-passing repro output verbatim.