skills.rest
sarkarshivaditya-lab
sarkarshivaditya-labCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-merge

Validates CI checks, tests, reviews, and acceptance criteria before merging GitHub pull requests.

Updated Jan 1, 2026
Search Tags:#code review#pull request#github#verification#merge#gh cli#ci
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill verification-before-merge-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-merge
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/verification-before-merge
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill verification-before-merge-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging pull requests without complete verification leads to broken builds, unreviewed code, and unmet acceptance criteria reaching the main branch. This Skill enforces a hard gate that blocks any merge until every quality check passes. ## Core Features & Use Cases - Merge Gate Enforcement: Checks CI pipeline status, local integration tests, code review approval, unresolved conversations, branch freshness, and merge conflicts via the GitHub CLI. - Acceptance Criteria Verification: Confirms every acceptance criterion on the linked issue is checked before allowing the merge. - Post-Merge Cleanup: Closes the linked issue, updates project status, deletes local branches, and verifies deployment after merging. - Use Case: Before merging a feature PR, run the full pre-merge checklist to confirm CI is green, the review is approved, all conversations are resolved, and the branch is up to date, then squash-merge and clean up. ## Quick Start Verify that pull request 123 passes all merge gates and merge it if everything is green.

Frequently Asked Questions about verification-before-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a GitHub PR is ready to merge?▼

Run gh pr checks to confirm CI passes, gh pr view --json reviews to confirm approval, and gh pr view --json mergeable to check for conflicts. All gates including tests, review, and acceptance criteria must be green before merging.

How to verify CI checks pass before merging a pull request?▼

Use gh pr checks [PR_NUMBER] to list all CI check statuses such as build, lint, test, typecheck, and security. If any check fails, resolve the failures and wait for the pipeline to turn green before merging.

What merge strategy should I use with gh pr merge?▼

Squash merging creates a single clean commit and suits most PRs, merge commits preserve full history, and rebase gives linear history without a merge commit. Follow your project's conventions when choosing.

Why is my pull request blocked from merging?▼

Common blockers include failing CI checks, missing review approval, unresolved review conversations, an out-of-date branch, or merge conflicts. Check each gate with gh pr view and gh pr checks, then fix the failing condition.

Can I merge a PR when local integration tests have not run?▼

No. If the project has docker-compose services, local integration tests must pass against real services and migrations must apply successfully before merging. Relying on CI to discover integration bugs is not acceptable.

Related Skills

Explore More Software Engineering Skills→
kanade0404kanade0404

issue-driven-development

Convert a GitHub issue into a pull request with validated acceptance criteria.

Community
Advanced
khwerhahnkhwerhahn

close-issue

Close GitHub issues, linked pull requests, and feature branches.

Community
Advanced
microsoftmicrosoft
190.1k

fix-ci

Diagnose and resolve failed CI checks for the current session.

Official
Basic
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

Enforce small, frequent commits to the main branch for Trunk Based Development workflows.

Community
Advanced