[ak-bugsee]

Adds the Claude PR review caller (.github/workflows/claude-review.yml) to nextgen. It is the same file that is already on the default branch.

Why: GitHub runs pull_request workflows from the PR's base branch, so PRs that target nextgen get no review until the caller exists here. Reviews start on PRs opened or updated after this is merged (the review is skipped on this PR itself).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Lduv96TKHugriihj4RYUe6

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: f27160f9-aa2a-43d7-a6b5-1d4504c06066

📥 Commits

Reviewing files that changed from the base of the PR and between 8793584 and 0e304d6.

📒 Files selected for processing: 2

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

💤 Files with no reviewable changes: 1

• .github/workflows/claude.yml

Limit details: You’ve used all 10 included reviews currently available.

📝 Summary

Summary by CodeRabbit

• Automation
  • Pull requests now trigger an automated review when opened, updated, marked ready, reopened, or labeled.
  • The previous assistant workflow triggered by issue, pull request, and review mentions has been removed.

The change adds a workflow that invokes a reusable review workflow when a pull request is opened, synchronized, marked ready for review, reopened, or labeled. The job grants repository and check read access, pull-request and issue write access, and id-token: write, and passes CLAUDE_CODE_OAUTH_TOKEN. The change also removes the workflow that ran Claude Code in response to qualifying @claude mentions.

Priority: ⬇️ Low

Change: Feature

Merge Risk: ⚪ Minimal · up to 0e304

This adds automated PR reviews on the nextgen branch and removes the @claude mention workflow. No concrete merge-blocking issue was identified.

### Architecture Summary

Architecture risk: 🔵 Low · up to 0e304

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/claude-review.yml: Adds the Claude PR Review workflow, triggered by pull requests opened, synchronized, marked ready for review, reopened, or labeled.
• observed — Modified behavior in .github/workflows/claude-review.yml: Adds a review job that calls the reusable workflow at bugsee/.github/.github/workflows/claude-review.yml@main. It grants the job read access to contents and checks, write access to pull requests and issues, id-token: write, and passes CLAUDE_CODE_OAUTH_TOKEN.
• observed — Modified behavior in .github/workflows/claude.yml: The workflow that handled @claude mentions on issue comments, pull-request review comments, reviews, and issues was removed. It ran on a matching mention, checked out the repository, and invoked Claude Code with the configured OAuth secret, read access to contents and Actions, and write access to issues and pull requests.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies the main change: adding Claude pull request review to the nextgen branch.
Description check		The description directly explains the workflow addition, its purpose, and when reviews will start.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Usage-based review receipt

• Mode: Continue automatically
• Reviewed files: 1
• Waived: $0.25 (charged $0.00)
• View usage details

Note

This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews.

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

[claude]

Claude finished @ak-bugsee's task in 13s —— View job

---

Review of PR #16

I found no real issues in this PR, so I posted no inline comments.

What I checked

• .github/workflows/claude-review.yml is byte-identical to the one on origin/main. Both have blob SHA 2c5e64f.
• Deleting claude.yml matches main. Commit 75df3b1 on main ("add Claude PR review, drop @claude mention handler") also removed it. This brings nextgen in line with main.
• The caller grants only the permissions the called workflow needs: contents: read, pull-requests: write, issues: write, checks: read and id-token: write. It uses no pull_request_target, so a fork PR does not get write access or secrets.
• The reusable workflow is pinned to @main of bugsee/.github. That is a moving ref, but it is the org's own repo and the same choice as on main.
• I did not run any tests or tools. This is a CI-only change with no source impact.

Notes (not blockers)

• labeled is in the trigger types, so adding any label re-runs the review. That is probably intended, but it costs a review run per label.
• The review is skipped on this PR itself, as the description says. The first real check will be the next PR opened against nextgen.
• Removing claude.yml also removes the @claude mention handler from nextgen. This matches main, but note that issue and PR @claude mentions are only handled from the default branch's workflows.

Overall risk: Low

Merge recommendation: Approve and merge. This is a straight sync of the workflow state from main.

Most important issues to fix: None.

Positives

• The permissions are scoped narrowly and commented.
• The change matches the default branch, so there is no divergence in CI behavior.