wa:validate-merge

Validate PR approval and CI checks, then merge into the target branch.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:validate-merge
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/validate-merge
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

wa:validate-merge prevents broken or unapproved pull requests from being merged by verifying approvals, CI status, and mergeability before performing the merge.

Core Features & Use Cases

  • PR approval and CI gate enforcement: Confirms the PR is approved and that required checks are passing before any merge occurs.
  • Merge conflict detection with safe handling: Detects conflicting merge states and stops without auto-resolving, guiding you to fix conflicts manually.
  • Configurable merge strategy with confirmation: Supports merge commit, squash, and fast-forward-only modes, including a mode-calibrated default and a user confirmation step.

Use Case: You have an approved feature branch with CI passing, and you want to merge it into the integration/main branch using a specific strategy (e.g., squash) while guaranteeing it won’t fail due to conflicts or missing approvals.

Quick Start

Run /wa:validate-merge 42 --squash to validate PR 42 and merge it using a squash strategy after it passes approval and CI checks.

Frequently Asked Questions about wa:validate-merge

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

FAQPage Schema
How do I validate a pull request has approvals and passing CI before merging?

To validate pull request approvals and CI checks before merging, this Skill queries tracker:pr-view to confirm reviewDecision and statusCheckRollup are passing, ensuring unapproved or failing branches are never merged.

Can I enforce a specific git merge strategy when promoting an approved PR to main?

Yes, you can enforce a specific git merge strategy by passing arguments like --squash to the command, which applies a mode-calibrated merge commit, squash, or fast-forward-only strategy to the target integration branch.

What happens if there are merge conflicts during an automated pull request validation?

If merge conflicts are detected during pull request validation, the Skill checks the PR mergeable state and stops the process immediately without auto-resolving, requiring you to fix the conflicts manually before retrying the merge.

How do I prevent unapproved pull requests from being merged into the integration branch?

You prevent unapproved pull requests from being merged by running this Skill, which refuses conflicting or unapproved merges by verifying the PR reviewDecision and CI status before executing git:merge or git:ff-merge-to-main.

Does this PR validation tool auto-resolve git conflicts during the merge process?

No, this PR validation tool does not auto-resolve git conflicts; it explicitly detects conflicting merge states and halts the merge execution, guiding you to manually resolve the issues before attempting the integration again.