From 1760347dc76e45282880f89da2827bba0346a632 Mon Sep 17 00:00:00 2001 From: Bohdan Triapitsyn Date: Fri, 28 Aug 2026 14:12:35 +0300 Subject: [PATCH] docs(agents): prior maintainer verdicts are binding across triage sweeps A sweep verifies whether an earlier push-back or recorded product decision was addressed at the current HEAD and reports that explicitly; it never re-decides or re-asks. The generic rebase-request is never posted over an existing substantive review comment. --- .agents/skills/triage-prs/SKILL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.agents/skills/triage-prs/SKILL.md b/.agents/skills/triage-prs/SKILL.md index a0e5a57e..875e9430 100644 --- a/.agents/skills/triage-prs/SKILL.md +++ b/.agents/skills/triage-prs/SKILL.md @@ -7,6 +7,8 @@ Turn an unbounded PR queue into a short list of maintainer decisions. The pipeli Companion: each substantive review inside phase 3 applies the `pr-review` skill; this skill owns only the batch mechanics around it. +**The timeline outranks the snapshot.** Before any verdict or comment on a PR, read its existing comments: a prior maintainer verdict (a push-back list, a recorded product decision like a placement or scope call) is BINDING — a new sweep verifies whether it was addressed at the current HEAD and says so explicitly ("all three prior items resolved" / "item 2 still open"), never re-decides it or asks the maintainer the same product question again. And never post the generic rebase-request on a PR that already carries a substantive review comment — the author already has their instructions; a bare "please rebase" on top reads as the left hand not knowing the right. + ## Phase 1 — Mechanical sweep (no judgment, no LLM verdicts) Fetch all open PRs with `gh` (the repo is `openchamber/openchamber`). Two measurement rules learned the hard way: