Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Predicts whether a GitHub pull request will get merged by analyzing it across technical, hygiene, architectural, review, process, and social factors. Uses a shell script to gather PR data via the GitHub CLI and applies a rejection vector taxonomy to estimate merge likelihood.
Combines CI status, PR size, author merge history, review sentiment, and process compliance into a single scored report instead of checking each signal manually.
When to use it
- Checking if a stalled PR has blockers before pinging maintainers
- Evaluating an open-source contribution's chances before submitting
- Spotting why a team PR hasn't moved after two weeks
- Assessing a PR for unaddressed review feedback before re-requesting review
- Auditing a batch of open PRs to triage which need attention
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Will this PR get merged? https://github.com/vercel/next.js/pull/12345
- 1Run merge-check.sh with the PR URL to collect GitHub data as a single JSON object
- 2Parse CI check results, diff stats, review status, labels, and author history from the output
- 3Evaluate all analysis dimensions: technical signals, PR hygiene, architectural fit, review status, process compliance, and social signals
- 4Produce a structured mergeability report with a scored verdict and ranked risk factors
A report with a 🟢/🟡/🔴 mergeability score, ordered risk factors, strengths, actionable recommendations, and a one-sentence verdict
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.