[jleechan2015]

Companion to jleechanorg/.github PR #13. Removes hardcoded || '#worldai-bugs' fallback so the per-repo routing table (SOUL.md COMMIT hermes-tag-webhook-per-repo-routing) applies via auto-routing.

- slack_channel: ${{ vars.HERMES_SLACK_CHANNEL || '#worldai-bugs' }}
+ slack_channel: ${{ vars.HERMES_SLACK_CHANNEL }}

Refs: jleechan-7jrd

---

Note

Low Risk
Single-line CI notification routing change with no application or security impact; misconfiguration could send Hermes alerts to the wrong channel or omit a channel if the variable and auto-routing are both unset.

Overview
Removes the hardcoded || '#worldai-bugs' fallback on the slack_channel input passed into the reusable Hermes PR tag listener workflow.

slack_channel is now only vars.HERMES_SLACK_CHANNEL, so when that repo variable is unset the caller no longer forces #worldai-bugs and routing can follow the per-repo table in the shared workflow (companion to jleechanorg/.github PR #13).

^{Reviewed by Cursor Bugbot for commit 03f7cc8. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_d6a88122-96fe-49a1-94f6-f846f572c85e)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 53 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 26bb261a-16bb-483e-88d4-240abf7524be

📥 Commits

Reviewing files that changed from the base of the PR and between 26473db and 03f7cc8.

📒 Files selected for processing (1)

• .github/workflows/hermes-pr-tag-listener.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/drop-worldai-bugs-fallback

---

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