sdlc-merge-pr

Merges a verified pull request after validating promoted SHA, reviews, checks, and UAT gates.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-merge-pr-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-merge-pr
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-merge-pr
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-merge-pr-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging pull requests without verifying that the reviewed and promoted commit matches the current remote head risks shipping unreviewed or drifted code. This Skill enforces a guarded merge step inside the Agentic SDLC workflow so only the exact reviewed SHA is merged after all readiness gates pass. ## Core Features & Use Cases - SHA-Verified Merge: Requires the local clean HEAD, promoted SHA, reviewed PR head, and current remote PR head to be identical before merging. - Canonical Merge Command: Builds one exact gh pr merge command with --match-head-commit and an explicit strategy, rejecting admin bypass, branch deletion, and compound commands. - Short-Lived Authorization: Writes a scoped merge-authorization.json with expiry, expected head, base branch, and readiness statuses immediately before execution. - Use Case: After an Agentic SDLC run completes review and UAT, the coordinator invokes this Skill to merge the PR only when checks, reviews, branch state, and UAT evidence all pass. ## Quick Start Ask the agent to merge a specific pull request by number or URL only after confirming the promoted and reviewed SHA matches the current remote head.

Frequently Asked Questions about sdlc-merge-pr

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

FAQPage Schema
How do I safely merge a GitHub pull request after code review?

Verify that checks, required reviews, branch state, and UAT all pass, then confirm the current remote PR head equals the reviewed commit. Merge with gh pr merge using --match-head-commit so GitHub rejects the merge if the head has drifted.

What does gh pr merge --match-head-commit do?

The --match-head-commit flag makes the GitHub CLI merge only if the PR's current head matches the specified SHA. This prevents merging code that changed after review, closing the gap between approval and merge execution.

Can this skill merge a PR without explicit user approval?

No. The skill requires an explicit human merge request and verified coordinator workflow context. Missing approval or an expired merge-authorization.json maps to a POLICY_BLOCK failure and no merge is attempted.

Why does a guarded PR merge fail with head drift?

Head drift occurs when the local HEAD, promoted SHA, reviewed head, or remote PR head disagree, meaning code changed after review. The skill classifies this as PR_HEAD_DRIFT and requires human input instead of merging or overwriting.

When should I not use an automated guarded merge workflow?

Do not use it for PR creation or review, which belong to separate skills, or when you need to override branch protection, force merge, or delete branches. Those actions are explicitly blocked by the merge policy.