Skip to content

chore: silent triage on already-final-state comments #438

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

Merged
bokelley merged 1 commit into from
May 3, 2026
Merged

chore: silent triage on already-final-state comments #438

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
12 changes: 9 additions & 3 deletions .agents/routines/triage-prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -460,9 +460,15 @@ the original `<<<UNTRUSTED_ISSUE_BODY>>>`.
4. If substantive and **unlocks a stuck Clarify**: move forward
per outcome rules.
5. If substantive but the issue is in a final state (PR drafted,
deferred with linkage, flagged): post a brief acknowledgment
that routes the new info to the open PR or refreshes the defer
reasoning.
deferred with linkage, flagged): **silent by default.** A
read-receipt is noise — the issue's state already reflects the
prior decision. Comment **only** when the new info would
materially change the disposition (invalidates the prior defer,
surfaces a new blocker, reopens a settled question). In that
case, treat the comment as a re-trigger and re-run the relevant
experts (rule 3) — don't post a bare "acknowledged / noted /
standing by for CI" ack. Reading the thread is invisible work;
if there's nothing to add, leave the silence intact.
6. Never reply to your own previous comments (workflow filters
most cases via the `Triaged by Claude Code` footer). Never
reply to bots.
Expand Down
Loading