Pr Verify

REPO is detected automatically at runtime — do not hardcode it:

REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')

Worktree path: always /tmp/aionui-verify-<PR_NUMBER> — never use /tmp/aionui-pr-* (reserved for pr-automation/pr-fix).

Steps

Step 1 — PR List Display

Parse $ARGUMENTS for an optional PR number.

If a PR number is provided: skip the list, jump directly to Step 2 with that PR number.

If no argument provided: query bot:ready-to-merge PRs from the last PR_DAYS_LOOKBACK days (default 7):

DAYS=${PR_DAYS_LOOKBACK:-7}
gh pr list \
  --state open \
  --label "bot:ready-to-merge" \
  --search "created:>=$(date -v-${DAYS}d '+%Y-%m-%d' 2>/dev/null || date -d "${DAYS} days ago" '+%Y-%m-%d') -is:draft" \
  --json number,title,labels,changedFiles,additions,deletions,headRefName,baseRefName,commits,createdAt,author \
  --limit 50

If the result is empty: display 没有找到 bot:ready-to-merge 的 PR。 and exit.

For each PR, infer the type from the first commit message prefix:

Display as a numbered table:

# | PR   | 标题                              | 变更          | 类型
--|------|-----------------------------------|---------------|--------
1 | #123 | fix(auth): handle token expiry    | +45 / -12     | bugfix
2 | #124 | feat(ui): add dark mode toggle    | +230 / -18    | feature

Then prompt:

请输入序号选择 PR，或输入 q 退出：

• User inputs a number → use that PR
• User inputs q → exit

Save the selected PR number as PR_NUMBER for all subsequent steps.

Step 2 — Pre-flight Checks

Run three checks in order. A failure in any check presents the user with an action choice.

Check 1 — New Commits Since Ready-to-Merge Label

# Time when bot:ready-to-merge label was last set (infer from bot comment)
LABEL_SET_TIME=$(gh pr view $PR_NUMBER --json comments \
  --jq '[.comments[] | select(.body | test("<!-- pr-automation-bot -->") and (test("bot:ready-to-merge") or test("已自动 review") or test("已自动修复")))] | last | .createdAt // ""')

LATEST_COMMIT_TIME=$(gh pr view $PR_NUMBER --json commits \
  --jq '.commits | last | .committedDate')

If LATEST_COMMIT_TIME > LABEL_SET_TIME (new commits after the label was set), prompt:

⚠️ 该 PR 在标记 bot:ready-to-merge 后有新提交（最新提交：<LATEST_COMMIT_TIME>，标签时间：<LABEL_SET_TIME>）。 建议重新 review 后再合并。请选择： r - 移除 bot:ready-to-merge 标签，触发重新 review c - 忽略并继续验证

• r → remove bot:ready-to-merge label:

  gh pr edit $PR_NUMBER --remove-label "bot:ready-to-merge"
  

  Display 已移除标签，PR 将在下一轮自动化中重新 review。 and return to list (Step 1).
• c → continue to Check 2.

Check 2 — CI Status

gh pr view $PR_NUMBER --json statusCheckRollup \
  --jq '.statusCheckRollup[] | {name: .name, status: .status, conclusion: .conclusion}'

Required jobs: Code Quality, Unit Tests (ubuntu-latest), Unit Tests (macos-14), Unit Tests (windows-2022), Coverage Test, i18n-check

Informational exclusions: codecov/patch and codecov/project are informational — exclude them from all failure checks.

CI still running prompt:

⏳ 以下 CI job 尚未完成：[job 列表] 请选择： w - 等待 CI 完成后继续（推出，请稍后重新运行） c - 忽略，继续验证

• w → exit
• c → continue to Check 3

CI failed prompt:

❌ 以下 CI job 未通过：[job 列表及结论] 请选择： s - 跳过此 PR c - 忽略失败，继续验证

• s → remove bot:ready-to-merge label (let pr-automation re-process next round), return to list (Step 1):

  gh pr edit $PR_NUMBER --remove-label "bot:ready-to-merge"
  

• c → continue to Check 3

Check 3 — Merge Conflicts

gh pr view $PR_NUMBER \
  --json mergeable,mergeStateStatus,headRefName,baseRefName \
  --jq '{mergeable, mergeStateStatus, head: .headRefName, base: .baseRefName}'

Auto-merge attempt on conflict:

Why merge instead of rebase? Since we squash-merge all PRs, the intermediate commit history is irrelevant. git merge produces exactly the conflicts GitHub shows (one pass over the final diff), while git rebase replays each commit individually, often creating extra conflicts in files that GitHub reports as clean. Always use merge for conflict resolution in this workflow.

REPO_ROOT=$(git rev-parse --show-toplevel)
WORKTREE_DIR="/tmp/aionui-verify-${PR_NUMBER}"

# Clean up any stale worktree
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

# Detect fork vs same-repo PR
HEAD_OWNER=$(gh pr view $PR_NUMBER --json headRepositoryOwner --jq '.headRepositoryOwner.login')
REPO_OWNER=$(gh repo view --json owner --jq '.owner.login')
IS_FORK=$( [ "$HEAD_OWNER" != "$REPO_OWNER" ] && echo true || echo false )

# Fetch PR head into a named ref (avoids FETCH_HEAD overwrite)
git fetch origin pull/${PR_NUMBER}/head:refs/pr/${PR_NUMBER}
git worktree add "$WORKTREE_DIR" refs/pr/${PR_NUMBER} --detach

ln -sf "$REPO_ROOT/node_modules" "$WORKTREE_DIR/node_modules"

cd "$WORKTREE_DIR"
git fetch origin <base_branch>
git merge origin/<base_branch> --no-edit

If merge succeeds (no conflicts):

# Determine push target
if [ "$IS_FORK" = "true" ]; then
  FORK_URL="https://github.com/${HEAD_OWNER}/$(gh repo view --json name --jq '.name').git"
  git remote add fork-target "$FORK_URL" 2>/dev/null || true
  git fetch fork-target <head_branch>
  git push fork-target HEAD:refs/heads/<head_branch> --force-with-lease
else
  git push origin HEAD:refs/heads/<head_branch> --force-with-lease
fi

cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

gh pr merge $PR_NUMBER --squash --auto

Display 已自动解决冲突并推送，PR 已设置 auto-merge，等待 CI 通过后自动合并。 and skip to next PR (return to Step 1).

If merge has conflicts, attempt manual resolution:

Read each conflicting file and resolve the conflicts by understanding both sides of the change. After resolving all conflicts:

cd "$WORKTREE_DIR"
git add <resolved_files>
git commit --no-edit

If resolution succeeds → push (same fork-aware logic as above) and set --squash --auto.

If resolution fails or conflicts are too complex:

cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

Prompt:

❌ 合并冲突无法自动解决。请选择： m - 提示作者手动解决冲突 s - 跳过此 PR r - 标记为 bot:needs-human-review

• m → post comment to PR:

  gh pr comment $PR_NUMBER --body "<!-- pr-verify-bot -->
  
  ## 合并冲突（无法自动解决）
  
  本 PR 与目标分支存在冲突，无法自动解决。请手动 merge 或 rebase 后重新 push：
  
  \`\`\`bash
  git fetch origin
  git merge origin/<base_branch>
  # 解决冲突后
  git push
  \`\`\`"
  

  Then add label:

  gh pr edit $PR_NUMBER --remove-label "bot:ready-to-merge" --add-label "bot:needs-rebase"
  

  Return to list (Step 1).

• s → add bot:needs-rebase label and comment, return to list (Step 1):

  gh pr edit $PR_NUMBER --remove-label "bot:ready-to-merge" --add-label "bot:needs-rebase"
  gh pr comment $PR_NUMBER --body "<!-- pr-verify-bot -->
  PR 存在合并冲突，无法自动解决。请作者手动解决后重新 push。"
  

• r → add label and return to list:

  gh pr edit $PR_NUMBER --remove-label "bot:ready-to-merge" --add-label "bot:needs-human-review"
  

  Return to list (Step 1).

Step 3 — Review Summary Display

Fetch and display a concise summary of the existing review.

# Fetch review comment(s)
gh pr view $PR_NUMBER --json comments \
  --jq '[.comments[] | select(.body | startswith("<!-- pr-review-bot -->"))] | last | .body'

Parse from the review comment:

• 结论 (APPROVED / CONDITIONAL / review conclusion line)
• 问题数量 per severity level (CRITICAL / HIGH / MEDIUM / LOW)
• If a <!-- pr-fix-verification --> comment exists, also parse fix results

# Fetch fix verification comment if present
gh pr view $PR_NUMBER --json comments \
  --jq '[.comments[] | select(.body | startswith("<!-- pr-fix-verification -->"))] | last | .body'

Fetch changed files:

gh pr view $PR_NUMBER --json files \
  --jq '.files[] | {path: .path, additions: .additions, deletions: .deletions, status: .changeType}'

Check critical path:

if [ -n "$CRITICAL_PATH_PATTERN" ]; then
  CRITICAL_FILES=$(gh pr view $PR_NUMBER --json files \
    --jq '[.files[].path]' | jq -r '.[]' | grep -E "$CRITICAL_PATH_PATTERN" || true)
  [ -n "$CRITICAL_FILES" ] && HAS_CRITICAL_PATH=true || HAS_CRITICAL_PATH=false
else
  HAS_CRITICAL_PATH=false
  CRITICAL_FILES=""
fi

Display concise summary:

=== PR #<PR_NUMBER>: <标题> ===

作者: <author>  |  基分支: <base>  |  变更: +<add> / -<del>

Review 结论: ✅ 批准合并 / ⚠️ 有条件批准 / ❌ 需要修改
问题数量: CRITICAL(0) HIGH(1) MEDIUM(2) LOW(3)
修复状态: ✅ 已修复 2 个 / ⏭️ 驳回 1 个  [若有 pr-fix 报告]

变更文件 (N 个):
  src/renderer/features/auth/AuthModal.tsx  +45 / -12
  src/common/utils/token.ts                 +23 / -5
  ...

核心路径: ⚠️ 涉及核心路径文件  [若 HAS_CRITICAL_PATH=true]
           src/process/channels/auth.ts

Then prompt:

d - 查看完整 review 报告 | 回车继续影响分析

• d → display full review comment text, then re-show this prompt
• Enter → continue to Step 4

If no <!-- pr-review-bot --> comment found, display:

⚠️ 未找到 review 报告。该 PR 可能未经过自动化 review 流程。

And continue to Step 4.

Step 4 — Impact Analysis + Test Supplementation

4a — Worktree Setup

Create worktree at /tmp/aionui-verify-<PR_NUMBER> (reuse if already created in Step 2):

REPO_ROOT=$(git rev-parse --show-toplevel)
WORKTREE_DIR="/tmp/aionui-verify-${PR_NUMBER}"

# Reuse existing worktree if present, otherwise create
if [ ! -d "$WORKTREE_DIR" ]; then
  # Use a named ref to avoid FETCH_HEAD being overwritten by subsequent fetches
  git fetch origin pull/${PR_NUMBER}/head:refs/pr/${PR_NUMBER}
  git worktree add "$WORKTREE_DIR" refs/pr/${PR_NUMBER} --detach
  ln -sf "$REPO_ROOT/node_modules" "$WORKTREE_DIR/node_modules"
fi

4b — Impact Analysis

Parse changed files from the worktree:

cd "$WORKTREE_DIR"
BASE_REF=$(gh pr view $PR_NUMBER --json baseRefName --jq '.baseRefName')
CHANGED_FILES=$(git diff origin/${BASE_REF}...HEAD --name-only)

For each changed file, trace upstream dependencies (up to 2 levels):

• Read the changed file, identify what it exports (functions, components, constants, types)
• Search for files that import from this changed file:

  cd "$WORKTREE_DIR"
  # Level 1 — direct importers
  grep -rl "from.*<relative_module_path>" src/ --include="*.ts" --include="*.tsx" 2>/dev/null
  

• For each Level 1 importer, find Level 2 importers similarly

Build an impact map:

Changed:   src/common/utils/token.ts
  ↳ L1: src/renderer/features/auth/AuthModal.tsx
         src/process/channels/auth.ts
  ↳ L2: src/renderer/app/App.tsx (via AuthModal)
         src/process/main.ts (via auth channel)

UI rendering impact detection: flag any changed files in src/renderer/ or any L1/L2 impacted files that are React components (contain JSX or export default function/export const ... = () =>).

Test coverage check per path:

cd "$WORKTREE_DIR"
# Check if test files exist for each changed file
for FILE in $CHANGED_FILES; do
  BASENAME=$(basename "$FILE" | sed 's/\.[^.]*$//')
  DIRNAME=$(dirname "$FILE")
  # Look for co-located tests or __tests__ directory
  TEST_EXISTS=$(find "$WORKTREE_DIR/$DIRNAME" -name "${BASENAME}.test.*" -o -name "${BASENAME}.spec.*" 2>/dev/null | head -1)
  TESTS_DIR=$(find "$WORKTREE_DIR/$DIRNAME/__tests__" -name "${BASENAME}*" 2>/dev/null | head -1)
done

4c — Test Supplementation

For changed files with coverage gaps, write supplemental tests in the worktree. Do NOT commit or push these tests automatically — they are written to the worktree only for local validation.

Test writing rules:

• Each test file goes in <original_dir>/__tests__/<basename>.verify.test.ts
• Tests needing external API keys use test.skipIf(!process.env.KEY) guard
• Each test is annotated in a comment:
  • // [commit] — this test fills a genuine coverage gap and should be committed
  • // [skip] — this test is verification-only, not needed in the PR
• Test style matches existing tests in the project (Vitest, no .only, proper cleanup)

Example supplemental test structure:

import { describe, it, expect, vi } from 'vitest';
import { functionUnderTest } from '../token';

describe('token (supplemental verify)', () => {
  // [commit] fills coverage gap: expiry edge case not tested
  it('returns null when token is expired', () => {
    // ...
  });

  // [skip] integration path requires running process — verify only
  it.skipIf(!process.env.INTEGRATION_TEST)('round-trips through IPC', () => {
    // ...
  });
});

4d — Run Test Suite

cd "$WORKTREE_DIR"
bun run test

Capture test results: total, passed, failed, skipped. If tests fail, note which files are failing.

Step 5 — Verification Report

Calculate confidence level based on impact analysis and test results:

Display the full verification report:

=== 验证报告：PR #<PR_NUMBER> ===

## 影响分析

变更文件 (N 个):
  [list of changed files]

上游影响:
  L1 直接依赖: N 个文件
  L2 间接依赖: N 个文件
  [impact map summary]

UI 渲染影响: ✅ 无 / ⚠️ 涉及 N 个组件

核心路径: ✅ 未涉及 / ⚠️ 涉及 [file list]

## 测试结果

全量测试: ✅ 通过 / ❌ 失败
  通过: N  |  失败: N  |  跳过: N

覆盖情况:
  [list files with/without tests]

补充测试建议 (N 个):
  ✅ [commit] src/common/utils/__tests__/token.verify.test.ts — 3 个用例覆盖 expiry 边界
  ⏭️ [skip]  src/common/utils/__tests__/token.verify.test.ts — 1 个集成用例，仅本地验证

## 综合置信度

🟢 HIGH / 🟡 MEDIUM / 🔴 LOW
[1 句话说明原因]

Then display action menu:

请选择操作：
  m  - 直接合并（squash merge）
  mt - 提交补充测试后合并
  v  - 手动验证（在本地运行应用后决策）
  r  - 拒绝合并（标记 bot:needs-human-review）
  s  - 跳过（不修改标签，返回列表）
  d  - 查看完整 review 报告

Step 6 — Action Execution

m — Direct Merge

gh pr merge $PR_NUMBER --squash

Clean up worktree:

cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

Display ✅ PR #<PR_NUMBER> 已合并。 then return to list (Step 1).

mt — Merge with Supplemental Tests

First, commit recommended tests ([commit]-annotated only) to the PR branch:

# Get head branch name
HEAD_BRANCH=$(gh pr view $PR_NUMBER --json headRefName --jq '.headRefName')

cd "$WORKTREE_DIR"
# Stage only [commit]-annotated test files
git add <commit-annotated test files>

# Infer scope from changed files (use first changed file's directory segment)
SCOPE=$(echo "$CHANGED_FILES" | head -1 | cut -d'/' -f3)

git commit -m "test(${SCOPE}): add supplemental tests for PR #${PR_NUMBER}"

Important: commit message must NOT contain Co-Authored-By or any AI signature.

Push to the PR head branch (fork-aware):

cd "$WORKTREE_DIR"

# Detect fork vs same-repo PR
HEAD_OWNER=$(gh pr view $PR_NUMBER --json headRepositoryOwner --jq '.headRepositoryOwner.login')
REPO_OWNER=$(gh repo view --json owner --jq '.owner.login')

if [ "$HEAD_OWNER" != "$REPO_OWNER" ]; then
  FORK_URL="https://github.com/${HEAD_OWNER}/$(gh repo view --json name --jq '.name').git"
  git remote add fork-target "$FORK_URL" 2>/dev/null || true
  git fetch fork-target "$HEAD_BRANCH"
  git push fork-target HEAD:refs/heads/${HEAD_BRANCH} --force-with-lease
else
  git push origin HEAD:refs/heads/${HEAD_BRANCH} --force-with-lease
fi

Then enable auto-merge (CI will re-run with the new test commit):

gh pr merge $PR_NUMBER --squash --auto

Clean up worktree:

cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

Display ✅ 已推送补充测试并设置 auto-merge。CI 通过后 PR #<PR_NUMBER> 将自动合并。 then return to list (Step 1).

v — Manual Verification

Display the command for the user to run in another terminal:

在另一个终端中运行以下命令启动应用进行验证：

  cd /tmp/aionui-verify-<PR_NUMBER> && bun run start

验证完成后，请在此选择：
  m  - 合并
  mt - 提交补充测试后合并
  r  - 拒绝合并
  s  - 跳过

Wait for user input and execute the corresponding action as defined in this step.

r — Reject

Prompt for reason:

请输入拒绝原因（将写入 PR 评论）：

Read reason from user input.

Update labels:

gh pr edit $PR_NUMBER --remove-label "bot:ready-to-merge" --add-label "bot:needs-human-review"

Post rejection comment:

gh pr comment $PR_NUMBER --body "<!-- pr-verify-bot -->

## 人工验证：未通过

本 PR 在 pr-verify 验证阶段被拒绝，需要人工 review。

**拒绝原因：** <user-provided reason>

**验证详情：**
- 置信度：🟢 HIGH / 🟡 MEDIUM / 🔴 LOW
- 测试结果：通过 N / 失败 N / 跳过 N
- 影响范围：L1 N 个文件，L2 N 个文件"

Clean up worktree:

cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

Display 已标记 bot:needs-human-review，PR #<PR_NUMBER> 已移交人工处理。 then return to list (Step 1).

s — Skip

No label change. Clean up worktree:

cd "$REPO_ROOT"
git worktree remove "$WORKTREE_DIR" --force 2>/dev/null || true

Return to list (Step 1).

d — View Full Review

Fetch and display the full content of the <!-- pr-review-bot --> comment. Stay on the current PR — re-show the action menu after displaying.

Step 7 — Cleanup and Session Summary

When user inputs q at the PR list, or the PR list is empty, or all PRs have been processed:

Clean up all verify worktrees:

for dir in /tmp/aionui-verify-*; do
  [ -d "$dir" ] && git -C "$(git rev-parse --show-toplevel)" worktree remove "$dir" --force 2>/dev/null || true
done

Display session summary:

=== pr-verify 会话总结 ===

✅ 已合并:        [#123 fix(auth): handle token expiry, ...]
🔄 Auto-merge 中: [#124 feat(ui): add dark mode toggle, ...]
❌ 已拒绝:        [#125 refactor(db): restructure schema, ...]
⏭️ 已跳过:        [#126 chore: update deps, ...]

共处理 N 个 PR。

Mandatory Rules

• Worktree path — always /tmp/aionui-verify-<PR_NUMBER>; never use /tmp/aionui-pr-* (reserved for pr-automation/pr-fix)
• No AI signature — no Co-Authored-By, no Generated with in any commit or comment
• Merge strategy — always --squash; never --merge or --rebase
• Comment marker — use <!-- pr-verify-bot --> (distinct from <!-- pr-review-bot --> and <!-- pr-automation-bot -->)
• REPO detection — REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner') — never hardcode
• Test push only on mt — supplemental tests are written to worktree only; never pushed unless user chooses mt
• Worktree reuse — if Step 2 auto-merge already created a worktree, reuse it in Step 4 instead of recreating
• Label atomicity — when swapping labels, do both in a single gh pr edit call
• Named refs over FETCH_HEAD — never rely on FETCH_HEAD (it is overwritten by every git fetch); always use refs/pr/<PR_NUMBER> or explicit branch names
• Merge over rebase for conflicts — use git merge (not git rebase) to resolve conflicts; rebase replays commits individually and creates spurious conflicts that GitHub does not show
• Fork-aware push — always detect fork PRs (headRepositoryOwner != repo owner) and push to the fork remote; never push fork branches to origin
• Fetch before force-with-lease — always git fetch <remote> <branch> before --force-with-lease to avoid "stale info" errors on new remotes
• Full refspec for push — always use HEAD:refs/heads/<branch> (not HEAD:<branch>) to avoid "not a full refname" errors on detached HEAD worktrees

Quick Reference

 1. Parse $ARGUMENTS → PR number or display bot:ready-to-merge list for selection
 2. Pre-flight (3 checks):
    a. New commits since ready-to-merge? → ask re-review or continue
    b. CI status? → all pass / running (ask wait/continue) / failed (ask skip/continue)
    c. Mergeable? → MERGEABLE (continue) / UNKNOWN (skip) / CONFLICTING (auto-merge or prompt)
 3. Review summary → parse pr-review-bot comment, show concise summary, d for full report
 4. Impact analysis + test supplementation:
    a. Create worktree at /tmp/aionui-verify-<PR> (reuse if from Step 2)
    b. Trace changed files → L1/L2 upstream deps → UI rendering impact
    c. Write supplemental tests in worktree (annotate [commit] vs [skip])
    d. bun run test in worktree
 5. Verification report → impact map, test results, supplemental test recs, confidence (🟢/🟡/🔴)
    Action menu: m / mt / v / r / s / d
 6. Action execution:
    m  → gh pr merge --squash, cleanup, back to list
    mt → commit [commit] tests, push to head branch, gh pr merge --squash --auto, cleanup, back to list
    v  → show bun run start command, wait for user, then m/mt/r/s menu
    r  → ask reason, remove bot:ready-to-merge + add bot:needs-human-review, post pr-verify-bot comment, cleanup
    s  → no label change, cleanup, back to list
    d  → show full review comment, re-show action menu
 7. Cleanup all /tmp/aionui-verify-* worktrees → session summary (merged/auto-merge/rejected/skipped)