fix: reliably trigger review chain when Claude bot opens PRs (pull_request opened missed)

[MervinPraison]

Summary

When praisonai-triage-agent[bot] opens a PR via claude.yml (gh pr create), the pull_request: opened event sometimes does not trigger downstream GitHub Actions. The full review chain (CodeRabbit → Copilot → FINAL @claude) never starts.

Example: PR #2245 — opened 2026-06-24 13:34:57 alongside #2243 and #2244 within ~11 seconds. #2243/#2244 got Auto PR Comment + full chain; #2245 got zero pull_request workflow runs and only a Greptile comment.

Manual unblock applied: FINAL @claude comment posted on #2245 — #2245 (comment)

---

Root cause

flowchart TD
  A[claude.yml creates PR via App token / GITHUB_TOKEN] --> B{pull_request opened fires?}
  B -->|Yes| C[bot-pr-trigger-reviews in auto-pr-comment.yml]
  C --> D["@coderabbitai + /review as MervinPraison PAT"]
  D --> E["@copilot → FINAL @claude"]
  B -->|No / dropped in burst| F[No workflows run]
  F --> G[Only external apps e.g. Greptile comment]
  G --> H[No @claude ever posted]

Loading

Contributing factors:

1. GitHub limitation: Events triggered by GITHUB_TOKEN (including GitHub App tokens used by claude-code-action for gh pr create) may not trigger new workflow runs on pull_request: opened.
2. Burst bot PR creation: When multiple bot PRs open within seconds, GitHub can drop/suppress events for later PRs in the batch (observed: 3rd PR in burst missed all workflows).
3. No fallback in claude.yml: After gh pr create, nothing uses GH_TOKEN PAT to kick the review chain.
4. Greptile is not wired into chain: auto-pr-comment.yml only chains off CodeRabbit/Qodo/Copilot — not Greptile alone.

Affected workflow: .github/workflows/auto-pr-comment.yml job bot-pr-trigger-reviews (requires pull_request: opened).

---

Required changes

1. Post-PR-create hook in claude.yml (primary fix)

After Claude runs gh pr create for issue fixes, add a final workflow step (only when a new PR was created) that uses secrets.GH_TOKEN (PAT as MervinPraison) to:

- name: Kick review chain for bot-created PR
  if: steps.check_fork.outputs.is_pr != 'true'  # issue flow that created PR
  env:
    GH_TOKEN: ${{ secrets.GH_TOKEN }}
  run: |
    PR_NUM=$(gh pr list --head "$BRANCH" --json number -q '.[0].number')
    # Same as bot-pr-trigger-reviews
    gh pr comment "$PR_NUM" --body '@coderabbitai review'
    gh pr comment "$PR_NUM" --body '/review'

Or consolidate into a shared actions/github-script step matching bot-pr-trigger-reviews logic (dedupe if comments already exist).

Also: use GH_TOKEN PAT for gh pr create itself (not App token) where possible — PAT-created PRs are more likely to trigger downstream workflows.

2. Idempotent review-chain helper in auto-pr-comment.yml

Extract bot-pr-trigger-reviews body into a reusable composite action or callable workflow (workflow_call) so both:

• pull_request: opened (existing path)
• claude.yml post-create step
• workflow_dispatch with pr_number input (manual recovery)

…can invoke the same logic without duplication.

3. Scheduled / recovery scanner (belt-and-braces)

Add a lightweight cron job (e.g. every 15 min) or extend existing merge-conflict scanner to find open bot PRs where:

• Author is praisonai-triage-agent[bot] or github-actions[bot]
• Opened > 10 min ago
• No @coderabbitai review comment from MervinPraison
• No FINAL @claude comment from MervinPraison

→ Post review-chain kick via PAT.

4. Optional: claude-fallback-timeout improvement

Current claude-fallback-timeout waits 15 min on pull_request: opened — useless if opened never fired. Change trigger to also run from recovery scanner or repository_dispatch.

---

Acceptance criteria

• Bot-created PR gets @coderabbitai review + /review within 2 min even when pull_request: opened does not fire
• Burst creation of 3+ bot PRs in <30s — all get review chain kick
• No duplicate @coderabbitai / @claude comments (dedupe guard)
• Manual recovery: gh workflow run bot-pr-recovery.yml -f pr_number=XXXX
• Document in .agent/workflows/review-chain.md

---

Test plan

1. Simulate bot PR create from claude.yml on a test issue; verify review comments appear without relying on pull_request: opened.
2. Open 3 bot PRs in rapid succession; confirm all receive chain kick.
3. Re-run scenario from fix: add runtime control surface commands to gateway bots #2245: PR with only Greptile comment → recovery scanner posts chain within 15 min.

---

Related

• Failed example: PR fix: add runtime control surface commands to gateway bots #2245
• Working example: PR feat: add runtime MCP server management to Agent #2243 (same batch, got full chain)
• Workflows: .github/workflows/claude.yml, .github/workflows/auto-pr-comment.yml

[praisonai-triage-agent]

Claude finished @MervinPraison's task —— View job

---

Issue #2251 — Reliably trigger review chain for bot-created PRs

• Read issue and understand request
• Review claude.yml and auto-pr-comment.yml
• Assess what changes are possible

---

⚠️ Permission limitation

Every required change in this issue lives under .github/workflows/ (claude.yml, auto-pr-comment.yml, new bot-pr-recovery.yml). My GitHub App token cannot create or modify files in .github/workflows/ — pushes touching that path are rejected by GitHub. So I can't open a PR that implements these workflow changes directly.

The one non-workflow deliverable (.agent/workflows/review-chain.md docs) can't stand alone without the workflow code it documents, so I'm providing the full ready-to-paste implementation below instead.

---

Root cause confirmed (from reading the workflows)

auto-pr-comment.yml job bot-pr-trigger-reviews (line 547) is gated entirely on pull_request: opened. When claude.yml creates a PR via gh pr create using the GitHub App token (claude.yml:246, app-token), GitHub suppresses the pull_request: opened event (events from GITHUB_TOKEN/App tokens don't cascade workflows). In bursts, later PRs also get dropped → no CodeRabbit/Qodo/Copilot/@claude chain ever starts. This matches PR #2245 (only Greptile commented).

---

Implementation guide (paste into the files — workflow edits must be done by a maintainer)

1. Post-PR-create kick in claude.yml

The claude-code-action step at claude.yml:244 runs gh pr create internally for issues. Add a step after it (only on the issue flow, is_pr != 'true') that uses the PAT to kick the chain idempotently:

      - name: Kick review chain for bot-created PR
        if: steps.check_fork.outputs.is_pr != 'true'
        env:
          GH_TOKEN: ${{ secrets.GH_TOKEN }}
          ISSUE_NUMBER: ${{ github.event.issue.number }}
        uses: actions/github-script@v7
        with:
          github-token: ${{ secrets.GH_TOKEN }}
          script: |
            const issueNum = parseInt(process.env.ISSUE_NUMBER, 10);
            const owner = context.repo.owner, repo = context.repo.repo;
            // Find PR opened for this issue branch (claude/issue-<n>-*)
            const { data: prs } = await github.rest.pulls.list({
              owner, repo, state: 'open', sort: 'created', direction: 'desc', per_page: 30
            });
            const pr = prs.find(p => p.head.ref.startsWith(`claude/issue-${issueNum}-`));
            if (!pr) { core.info('No PR created for this issue, skipping'); return; }
            const { data: comments } = await github.rest.issues.listComments({
              issue_number: pr.number, owner, repo, per_page: 100
            });
            const has = (txt) => comments.some(c =>
              c.body.includes(txt) &&
              (c.user.login === 'MervinPraison' || c.user.login === 'github-actions[bot]'));
            if (!has('@coderabbitai review')) {
              await github.rest.issues.createComment({ issue_number: pr.number, owner, repo, body: '@coderabbitai review' });
            }
            if (!has('/review')) {
              await github.rest.issues.createComment({ issue_number: pr.number, owner, repo, body: '/review' });
            }
            core.info(`Kicked review chain for PR #${pr.number}`);

This guarantees CodeRabbit + Qodo fire even when pull_request: opened never does. The existing copilot-after-coderabbit / copilot-after-qodo jobs (triggered by issue_comment, which DOES cascade under the PAT) then continue the chain to Copilot → @claude.

2. Dedupe guard in bot-pr-trigger-reviews (auto-pr-comment.yml:560)

Currently it posts @coderabbitai review + /review unconditionally. With the new claude.yml kick, both paths may fire → duplicates. Add the same idempotency check before posting:

            const { data: comments } = await github.rest.issues.listComments({
              issue_number: pr, owner, repo, per_page: 100 });
            const has = (txt) => comments.some(c => c.body.includes(txt) &&
              (c.user.login === 'MervinPraison' || c.user.login === 'github-actions[bot]'));
            if (!has('@coderabbitai review'))
              await github.rest.issues.createComment({ issue_number: pr, owner, repo, body: '@coderabbitai review' });
            if (!has('/review'))
              await github.rest.issues.createComment({ issue_number: pr, owner, repo, body: '/review' });

3. Recovery scanner — new file .github/workflows/bot-pr-recovery.yml

name: Bot PR Recovery
on:
  schedule:
    - cron: '*/15 * * * *'
  workflow_dispatch:
    inputs:
      pr_number:
        description: 'Specific PR number to kick'
        required: false
jobs:
  recover:
    runs-on: ubuntu-latest
    permissions:
      pull-requests: write
      issues: write
    steps:
      - name: Find and kick stalled bot PRs
        uses: actions/github-script@v7
        with:
          github-token: ${{ secrets.GH_TOKEN }}
          script: |
            const owner = context.repo.owner, repo = context.repo.repo;
            const manual = '${{ github.event.inputs.pr_number }}';
            let prs;
            if (manual) {
              const { data } = await github.rest.pulls.get({ owner, repo, pull_number: parseInt(manual,10) });
              prs = [data];
            } else {
              const { data } = await github.rest.pulls.list({ owner, repo, state: 'open', per_page: 100 });
              prs = data;
            }
            const tenMinAgo = Date.now() - 10*60*1000;
            const botAuthors = ['praisonai-triage-agent[bot]', 'github-actions[bot]'];
            for (const pr of prs) {
              if (!manual) {
                if (!botAuthors.includes(pr.user.login)) continue;
                if (new Date(pr.created_at).getTime() > tenMinAgo) continue;
              }
              const { data: comments } = await github.rest.issues.listComments({
                issue_number: pr.number, owner, repo, per_page: 100 });
              const byOwner = (txt) => comments.some(c => c.body.includes(txt) &&
                (c.user.login === 'MervinPraison' || c.user.login === 'github-actions[bot]'));
              if (byOwner('@coderabbitai review')) continue; // chain already kicked
              await github.rest.issues.createComment({ issue_number: pr.number, owner, repo, body: '@coderabbitai review' });
              await github.rest.issues.createComment({ issue_number: pr.number, owner, repo, body: '/review' });
              core.info(`Recovery: kicked review chain for PR #${pr.number}`);
            }

Manual recovery: gh workflow run bot-pr-recovery.yml -f pr_number=2245

4. Greptile-only fallback (optional)

claude-after-gemini already chains off Gemini. Greptile is only consulted in claude-fallback-timeout/claude-review-recovery aggregation. The recovery scanner (#3) covers the "only Greptile commented" case from #2245 since it doesn't depend on any reviewer activity.

---

Why I can't open the PR myself

GitHub App permissions do not allow workflow modifications — I cannot push files in .github/workflows/.

A maintainer can apply the four changes above. The logic is designed to be idempotent (dedupe guards on every post) so the pull_request: opened path and the new claude.yml/cron paths can all coexist without duplicate comments — satisfying the acceptance criteria.
• Branch: claude/issue-2251-20260624-1547