# Send Merge Check to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "merge-check", "name": "Merge Check", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/tag-assistant/merge-check", "canonicalUrl": "https://clawhub.ai/tag-assistant/merge-check", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/merge-check", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=merge-check", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/rejection-taxonomy.md", "scripts/merge-check.sh" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "merge-check", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-05T13:08:06.164Z", "expiresAt": "2026-05-12T13:08:06.164Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=merge-check", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=merge-check", "contentDisposition": "attachment; filename=\"merge-check-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "merge-check" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/merge-check" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/merge-check", "downloadUrl": "https://openagent3.xyz/downloads/merge-check", "agentUrl": "https://openagent3.xyz/skills/merge-check/agent", "manifestUrl": "https://openagent3.xyz/skills/merge-check/agent.json", "briefUrl": "https://openagent3.xyz/skills/merge-check/agent.md" } } ``` ## Documentation ### Merge Check Predicts whether a GitHub PR will get merged by analyzing it against a comprehensive rejection vector taxonomy. Not a generic code quality tool — this answers: "Will this PR get merged by the maintainer?" ### Quick Start Run the data gathering script: bash skills/merge-check/scripts/merge-check.sh owner/repo#123 # or bash skills/merge-check/scripts/merge-check.sh https://github.com/owner/repo/pull/123 Parse the JSON output Analyze against the dimensions below Produce the mergeability report ### Analysis Dimensions After gathering data, analyze across ALL of these dimensions. Load skills/merge-check/references/rejection-taxonomy.md for the detailed rejection vector framework. ### 1. Technical Signals (Automated Gates) CI status: Are all checks passing? Any failed or pending? Build status: Does it compile/build? Coverage: Any coverage regression indicated? ### 2. PR Hygiene Size (most predictive single factor): 🟢 <400 LOC changed — ideal, easy to review 🟡 400–1000 LOC — risky, reviewer fatigue 🔴 >1000 LOC — danger zone, likely to stall or get rejected File spread: Concentrated in one area or scattered across directories? Single concern: Does it do one thing, or is it a kitchen-sink PR? Title & description: Clear, descriptive? Or vague/empty? Linked issue: Does it reference an issue? (Signals intentionality) Commit hygiene: Clean messages? Reasonable count? Squash-ready? ### 3. Architectural Fit Pattern consistency: Does it follow repo conventions? (language, directory structure, naming) Dependencies: New dependencies introduced? (High friction signal) Scope creep: Does it touch things outside its stated purpose? File types: Consistent with repo's tech stack? ### 4. Review Status Approvals: Any already? How many required? Changes requested: Outstanding and unaddressed? (Strong rejection signal) Reviewer assignment: Are required reviewers assigned? Review comment sentiment: Positive, neutral, or adversarial? CODEOWNERS: Does the PR touch files with code owners? Are they reviewing? ### 5. Process Compliance Draft status: Draft PRs won't merge Blocking labels: WIP, do-not-merge, needs-work, etc. PR template: Was it followed? (Empty template = red flag) CLA/DCO: If repo requires it, is it signed? ### 6. Social/Meta Signals Author merge history: What % of this author's recent PRs were merged in this repo? Staleness: How long has it been open? (>2 weeks = concern, >30 days = likely abandoned) Activity level: Recent comments/updates, or radio silence? First-time contributor: Higher rejection rate for newcomers ### Output Format Produce a structured report: ### Mergeability Score 🟢 High (>80% likely to merge) — No blockers, reviews positive, CI green 🟡 Medium (40–80%) — Some concerns but addressable 🔴 Low (<40%) — Significant blockers present ### Report Sections Mergeability Score: 🟢/🟡/🔴 with percentage estimate Risk Factors: Bullet list of specific concerns, ordered by severity Strengths: What's working in the PR's favor Recommendations: Actionable steps to improve mergeability (if not already 🟢) Verdict: One-sentence summary ### Example Output ## PR Mergeability Report: owner/repo#123 **Score: 🟡 Medium (~55%)** ### Risk Factors - ⚠️ 847 lines changed — approaching reviewer fatigue threshold - ⚠️ Changes requested by @maintainer not yet addressed - ⚠️ Touches 12 files across 6 directories — scattered scope - ℹ️ No linked issue ### Strengths - ✅ All 14 CI checks passing - ✅ Clear title and detailed description - ✅ Author has 73% merge rate in this repo (8/11 recent PRs) - ✅ Active discussion — last update 2 hours ago ### Recommendations 1. Address @maintainer's review comments before requesting re-review 2. Consider splitting into smaller PRs (config changes vs logic changes) 3. Link the relevant issue for traceability ### Verdict Solid PR with passing CI and an active author, but stalled on unaddressed review feedback — resolving those comments is the critical path to merge. ### Script Reference The script (scripts/merge-check.sh) gathers all data via gh CLI and outputs a single JSON object with these keys: KeyContentsprFull PR metadata (title, body, author, state, draft, labels, reviewers)filesList of changed files with patch statsdiff_statsTotal additions, deletions, changed files countchecksCI/check run results for the head commitreviewsAll reviews (approved, changes_requested, commented)review_commentsInline review commentsissue_commentsPR conversation commentscommitsCommit list with messagesrepoRepository metadata (language, size, defaults)author_historyAuthor's recent closed PRs and merge ratehas_codeownersBooleanhas_contributingBoolean ### Error Handling The script outputs "error" fields when individual API calls fail (e.g., rate limits, 404s). Analyze what's available and note any missing data in the report. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: tag-assistant - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-05T13:08:06.164Z - Expires at: 2026-05-12T13:08:06.164Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/merge-check) - [Send to Agent page](https://openagent3.xyz/skills/merge-check/agent) - [JSON manifest](https://openagent3.xyz/skills/merge-check/agent.json) - [Markdown brief](https://openagent3.xyz/skills/merge-check/agent.md) - [Download page](https://openagent3.xyz/downloads/merge-check)