feat(iterate-pr): Distinguish review bots from informational bots#46
Merged
feat(iterate-pr): Distinguish review bots from informational bots#46
Conversation
Review bots (Sentry, Warden, Cursor, Bugbot, CodeQL, etc.) post actionable code feedback that was being silently ignored because all bot comments were dumped into a single "bot" bucket. Split bot classification so review bot feedback flows through LOGAF content categorization into high/medium/low with a review_bot flag, while informational bots (Codecov, Dependabot, etc.) remain in the bot bucket for silent skipping. Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.
Stop iterate-pr from silently ignoring actionable code review feedback from bots like Sentry, Warden, Cursor, Bugbot, and CodeQL.
Previously all bot comments were dumped into a single
botbucket that SKILL.md instructed to "skip silently." This meant real findings — security issues, lint violations, bugs — were never evaluated. Now bot classification is split into two categories:review_bot: trueflag, and are treated the same as human feedbackbotbucket for silent skippingThe
is_review_bot()check runs beforeis_info_bot()so usernames likesentry-autofix[bot]that match both^sentryand[bot]$are correctly classified as review bots.SKILL.md is updated to document the distinction: review bot feedback must be verified (fix real issues, explain false positives), while informational bot comments are still skipped silently.