Repository navigation
skills(review-reviewers): name pull_request_review self-trigger variant - #707
Merged
Merged
Conversation
The non-issues entry for tend-mention firing on the bot's own activity only named issue_comment events. The same self-trigger fires when the bot's own tend-review review mirrors back as pull_request_review; the review-reviewers carry tracked this variant and it has now crossed the codification threshold (4 occurrences in one cycle). Name it explicitly so future runs map it to the existing non-issue rather than re-analyzing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merged
max-sixty
added a commit
that referenced
this pull request
Jun 23, 2026
Bumps generator version to 0.1.7, syncs the lockfile, and adds the `## 0.1.7` CHANGELOG section (published verbatim as the GitHub Release notes on tag push). Changes since 0.1.6: pin actions/checkout to v7 with review opting into the fork-PR checkout guard (#725); bump claude-code to 2.1.185 (#719); running-in-ci surfaces blocking scope rules instead of routing around them (#717) and caps CI-poll loops to the Bash 10-min limit (#695); nightly workflow-regen bases its worktree on an open PR rather than branch-ref existence (#721); de-duplicate composite-action step bodies under shared/steps/ with harness-named action paths (#712); correct the codex effort list (#710); review-reviewers and worker-deploy doc fixes (#707, #711).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Name the
pull_request_reviewself-trigger variant explicitly in thereview-reviewersnon-issues entry fortend-mentionfiring on the bot's own activity.Why
The non-issues list already documents
tend-mentionself-triggering on the bot's ownissue_commentevents and silent-exiting, and states that sender/commenter-based filters are not the accepted shape (only label-based skips are). The same mechanism fires when the bot's owntend-reviewreview mirrors back as apull_request_reviewevent — but the entry only namedissue_comment, so the review-mirror variant wasn't covered by name.review-reviewershas been tracking this variant as a carry observation with an explicit codification threshold (≥3 occurrences). This hour it recurred 4× in a single cycle (run 27736348149), well past threshold:All four are the bot's own reviews (PRs authored by
max-sixty) firingpull_request_review→tend-mention, which then silent-exits via the self-conversation guard. This is correct, accepted behavior — the change only documents the variant so futurereview-reviewersruns map it to the existing non-issue instead of re-analyzing it or proposing a (rejected) sender filter.Scope
One-sentence addition to the existing entry. No behavioral change; the runtime self-trigger handling is unchanged and remains correct.
Evidence log (accumulated carry history): https://gist.github.com/530887e60f9483c8f094304bfe38ea57