Auto-respond to all PR review comments without @claude mention

[don-petry]

Summary

• Removed the contains(github.event.comment.body, '@claude') filter from the claude job's if condition
• Claude now automatically responds to all issue comments and PR review comments from trusted contributors (OWNER, MEMBER, COLLABORATOR)
• Added claude[bot] exclusion to prevent infinite feedback loops where Claude responds to its own comments

Motivation

When Claude creates PRs from issues (via the claude-issue job), reviewers currently have to explicitly mention @claude in their review comments for Claude to pick them up. This friction slows down the review cycle. With this change, Claude automatically addresses all review feedback from trusted contributors.

Test plan

• Verify Claude responds to a PR review comment without @claude mention
• Verify Claude does not trigger on its own comments (no infinite loop)
• Verify the author_association check still restricts triggers to OWNER/MEMBER/COLLABORATOR
• Verify the pull_request event trigger is unchanged

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 18 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 4 minutes and 18 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2e6098e8-45c2-4f30-8d7f-633058dc467d

📥 Commits

Reviewing files that changed from the base of the PR and between 7bdbb81 and 7ad269c.

📒 Files selected for processing (1)

• .github/workflows/claude-code-reusable.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch auto-respond-pr-reviews

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Updates the org-level reusable Claude Code workflow to trigger interactive Claude responses on trusted-contributor PR/issue comments without requiring an explicit @claude mention, while attempting to prevent bot self-reply loops.

Changes:

• Removes the contains(..., '@claude') gating for issue_comment and pull_request_review_comment triggers.
• Adds an exclusion for comments authored by claude[bot] to reduce the risk of self-trigger loops.
• Updates the job header comment to reflect the new interactive trigger behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

With the @claude mention gate removed, this job will now run much more frequently (potentially for every review comment from trusted users). The workflow currently has no concurrency configured for the claude job, so multiple comments in quick succession can start overlapping runs on the same PR, which can lead to conflicting pushes/comments and unnecessary compute/API usage. Consider adding a concurrency group keyed by PR number (or issue/PR number fallback) with cancel-in-progress: true to ensure only one interactive run per PR at a time.

Suggested change

	contains(fromJson('["OWNER","MEMBER","COLLABORATOR"]'), github.event.comment.author_association))
	contains(fromJson('["OWNER","MEMBER","COLLABORATOR"]'), github.event.comment.author_association))
	concurrency:
	group: ${{ format('claude-{0}', github.event.pull_request.number || github.event.issue.number || github.run_id) }}
	cancel-in-progress: true