merge-check
by tag-assistant
Coding Agents & IDEsBrief
Analyze a GitHub pull request for mergeability — predict whether it will get merged based on technical.
Description
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
User asks: Will this PR get merged? https://github.com/vercel/next.js/pull/12345
- 1
Run merge-check.sh with the PR URL to collect GitHub data as a single JSON object
- 2
Parse CI check results, diff stats, review status, labels, and author history from the output
- 3
Evaluate all analysis dimensions: technical signals, PR hygiene, architectural fit, review status, process compliance, and social signals
- 4
Produce 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
- GitHub CLI (gh) installed and authenticated
- GitHub account with read access to the target repository
Installation
clawhub install tag-assistant/merge-checkRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.