Pr Merge Readiness

PR Merge Readiness

Replaces the manual checklist of "is CI green? are reviews approved? does it conflict? did Sonar/CodeRabbit/Greptile finish? is the branch stale?" with a single skill that collects every signal and outputs one verdict.

Use When

• About to merge a PR and want one combined "ready / not ready" answer
• Reviewing many PRs in a batch and need a triage table
• Reviewing PRs from PR-Agent, CodeRabbit, or Greptile that already have third-party comments to reconcile

Do Not Use When

• The PR is still WIP and you know it isn't done — use ship later
• Only one signal matters (e.g., just need CI status) — use ci-watch directly
• The work is on a branch with no PR yet — use pr-flow to create one first

Inputs / Prereqs

• gh CLI authenticated for the repo
• PR number, URL, or current branch (defaults to current branch's open PR)
• --strict flag: fail on any non-passing signal, even informational ones

Workflow

1. Identify the PR

# Default to current branch's PR
PR=$(gh pr view --json number -q .number 2>/dev/null)
[ -z "$PR" ] && { echo "No open PR for current branch"; exit 1; }

# Or use explicit arg
[ -n "$1" ] && PR="$1"

gh pr view "$PR" --json title,headRefName,baseRefName,mergeable,mergeStateStatus,\
isDraft,reviewDecision,statusCheckRollup,labels,additions,deletions,changedFiles,\
updatedAt,author,url

2. Collect signals

Run all checks in parallel where possible. Each produces a status: PASS, WARN, FAIL, or SKIP (signal not applicable to this repo).

Signal 1: Draft state

gh pr view "$PR" --json isDraft -q .isDraft

Draft → FAIL (cannot merge a draft).

Signal 2: Mergeability and conflicts

gh pr view "$PR" --json mergeable,mergeStateStatus

mergeable: CONFLICTING → FAIL with the list of conflicting files. mergeStateStatus: BLOCKED → FAIL (required reviews missing or branch protection). mergeStateStatus: BEHIND → WARN (rebase/merge main needed). mergeStateStatus: CLEAN → PASS.

Signal 3: CI status

gh pr checks "$PR" --json name,state,conclusion,detailsUrl

Any FAILURE → FAIL with the failing check names. Any IN_PROGRESS/PENDING → WARN ("CI still running"). All SUCCESS → PASS.

For known-flaky-but-not-blocking checks, classify as WARN not FAIL (configurable per-repo via .claude/pr-checks-allow-flaky.txt if present).

Signal 4: Review decision

gh pr view "$PR" --json reviewDecision,reviewRequests

APPROVED → PASS. CHANGES_REQUESTED → FAIL with reviewer names. REVIEW_REQUIRED → WARN ("awaiting review from X"). No required reviewers → SKIP.

Signal 5: Branch staleness

gh pr view "$PR" --json baseRefName,headRefName
git fetch origin --quiet
BEHIND=$(git rev-list --count "origin/$(gh pr view "$PR" --json headRefName -q .headRefName)..origin/$(gh pr view "$PR" --json baseRefName -q .baseRefName)" 2>/dev/null)

Branch >50 commits behind base → WARN ("rebase recommended"). Branch >200 commits behind → FAIL ("rebase required, very stale").

Signal 6: Third-party reviewer comments

Detect which third-party reviewers exist on the repo and check each:

# All review comments
gh pr view "$PR" --json comments -q '.comments[] | {author: .author.login, body: .body[0:200]}'

# CodeRabbit
gh pr view "$PR" --json comments -q '.comments[] | select(.author.login == "coderabbitai") | .body' | head -20

# Greptile
gh pr view "$PR" --json comments -q '.comments[] | select(.author.login | startswith("greptile")) | .body' | head -20

# Sonar (status check, not comment)
gh pr checks "$PR" --json name,state,conclusion -q '.[] | select(.name | test("Sonar"; "i"))'

# Socket
gh pr checks "$PR" --json name,state,conclusion -q '.[] | select(.name | test("Socket"; "i"))'

For each found reviewer:

• Unaddressed 🛑 / "must fix" / "blocking" comments → FAIL
• Unaddressed suggestions / nits → WARN
• All resolved or only positive comments → PASS
• Reviewer not present on this repo → SKIP

Signal 7: PR size

gh pr view "$PR" --json additions,deletions,changedFiles

• <300 LOC, <10 files → PASS
• 300–1000 LOC or 10–25 files → WARN ("large — verify scope")

• 1000 LOC or >25 files → FAIL in --strict mode, WARN otherwise

Signal 8: Branch age

gh pr view "$PR" --json createdAt,updatedAt

Last update >7 days ago → WARN ("stale; rebase + re-verify before merge").

3. Compute verdict

Aggregate the signals:

In --strict mode, any WARN becomes FAIL.

4. Output the report

PR #1234 — <title>
Branch: feature/x → main  |  Author: @lucas  |  Updated: 2h ago

SIGNALS
  ✓ Not draft
  ✓ Mergeable (clean)
  ✓ CI: 12/12 checks passing
  ✓ Reviews: APPROVED by @reviewer
  ✓ Branch: 3 commits behind base
  ⚠ CodeRabbit: 2 unresolved suggestions
  ✓ PR size: 287 LOC, 8 files
  ✓ Branch age: updated 2h ago

VERDICT: WAIT
Reason: CodeRabbit has 2 unresolved suggestions. Resolve or explicitly dismiss
before merging. Run `/gh-address-comments` to handle them.

Suggested next action:
  /gh-address-comments  (then re-run this skill)

For MERGE:

VERDICT: MERGE
Suggested next action:
  gh pr merge 1234 --squash --delete-branch

For FIX:

VERDICT: FIX
Reason: CI check "test (backend)" is failing. Fix the failing test before merging.

Suggested next action:
  /gh-fix-ci  (or open the failing run: <detailsUrl>)

Outputs / Evidence

• One-page verdict (MERGE / WAIT / FIX)
• Per-signal status with actionable detail
• Suggested next skill or gh command to advance
• Does not actually merge — that remains an explicit user action

Failure / Stop Conditions

• gh not authenticated → report and stop
• Repo not found / PR number invalid → report and stop
• Network failure on any signal → mark that signal as WARN ("could not check") and continue; never silently treat unknown as PASS

Memory Hooks

• Read memory for any per-repo overrides (allow-flaky checks, third-party reviewer expectations) before computing the verdict
• Optional: write a one-line memory after a MERGE verdict was acted on, so trend data ("Lucky merged 12 PRs this week, 3 with WARN overridden") becomes available