Skip to content

pstack: bug-fix playbook gets a flake-triage rule #359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chesley-veko wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Open

pstack: bug-fix playbook gets a flake-triage rule #359

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions pstack/skills/poteto-mode/playbooks/bug-fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.