pr-merge-readinesslisted

# 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 ```bash # 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`, `FA