Expand Claude review workflow permissions and fix logger documentation

[DiamondDagger590]

Summary

This PR expands the Claude code review workflow's allowed tools to enable deeper git history inspection, and corrects the logging convention documentation to reflect the actual recommended pattern.

Changes

• Workflow permissions: Added Bash(git diff:*), Bash(git log:*), and Bash(git show:*) to the allowedTools list in both the scheduled and on-demand Claude review jobs. This enables Claude to inspect commit history and diffs beyond the current PR context, improving code review depth and context awareness.

• Logger documentation: Updated CLAUDE.md to correct the logging convention from the generic Logger.log() pattern to the more specific CorePlugin.getInstance().getLogger().log() pattern. This aligns the documentation with the actual recommended approach for routing stack traces through the server logger and preserving them in log aggregators.

Implementation Details

Both workflow job configurations (scheduled-review and on-demand-review) were updated identically to maintain consistency. The git-based tools allow Claude to:

• Compare changes across commits with git diff
• Inspect commit history with git log
• Examine specific commits with git show

This enables more thorough analysis of code changes in context of the repository's evolution.

https://claude.ai/code/session_017q76Se6Yvwmjow3t3FSLEX

[coderabbitai]

Warning

Review limit reached

@DiamondDagger590, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: QUIET

Plan: Pro

Run ID: 29b6f413-9b43-4fa8-92aa-dc86b4691edd

📥 Commits

Reviewing files that changed from the base of the PR and between a1a1a8e and 658053a.

📒 Files selected for processing (2)

• .github/workflows/claude-review.yml
• CLAUDE.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/quest-system-audit-july-3u9s9y

---

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.}