skills.rest
Levezze
LevezzeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

merge-pr

Merge pull requests after CI, deployment, and smoke checks.

1|Updated Jan 6, 2026
Search Tags:#pull request#database migrations#github#deployment validation#smoke testing#ci gating#production promotion
One-click install
npx skills add https://github.com/Levezze/devkit --skill merge-pr-levezze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/Levezze/devkit/tree/main/skills/merge-pr
Command: npx skills add https://github.com/Levezze/devkit --skill merge-pr-levezze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or incomplete pull request promotions by enforcing a full merge-and-promote verification sequence, including CI validation, required post-merge work, deploy waiting, and deployed smoke/e2e checks.

Core Features & Use Cases

  • Repository-agnostic gating: Detects the repo’s stack and chooses the right CI, migration, seed, build, health, and e2e commands based on project files and CLAUDE.md overrides.
  • Non-negotiable safety checks: Refuses to proceed on non-default PR bases, blocks merges when CI is red without explicit authorization, and requires explicit confirmation for destructive prod actions.
  • Two-phase promotion for production: After a successful main promotion, optionally forward-merges main → production with prod-specific deploy waiting, migrations/seeds, prod e2e, and prod smoke verification.

Quick Start

Run /merge-pr 489 to merge PR #489 into main with CI verification, post-merge migrations/seeds when applicable, wait for deployment, then validate the new revision with deployed smoke or e2e.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I safely merge a pull request only after CI passes and deployment is verified?▼

To safely merge a pull request with deploy validation, the merge process enforces CI gating, waits for post-merge deployment, and verifies the live revision using smoke and e2e checks before completing.

What happens to a pull request merge if CI checks are failing?▼

When CI checks are failing, the pull request merge is blocked by a strict stop-and-confirm behavior, requiring explicit authorization before proceeding to ensure unsafe promotions are prevented.

How can I automate database migrations and seeds during a GitHub pull request merge?▼

Automating database migrations and seeds during a pull request merge is handled by detecting project files and CLAUDE.md overrides, executing required post-merge work with explicit confirmation for destructive operations.

Does this pull request merge process support promoting code to a production branch?▼

Yes, the pull request merge process supports production promotion by forward-merging the default branch into production, applying prod-specific migrations, waiting for deployment, and running prod e2e validations.

Can I use automated deploy gating for pull requests across different tech stacks?▼

Yes, automated deploy gating works across varied tech stacks by detecting the package manager, CI configuration, health endpoints, and e2e harness conventions while honoring repo-specific overrides.

Why does a pull request merge require explicit confirmation for non-default bases?▼

Explicit confirmation for non-default bases is required during a pull request merge to prevent unintended branch promotions and ensure strict safety checks are honored before merging changes.

Related Skills

Explore More Software Engineering Skills→
kangmominkangmomin
1

hyeondong-init-hd

Configure all hyeondong-harness environment settings in a single run.

Community
Advanced
BedaBeda-GrowthBedaBeda-Growth

final-verify

Automate staging-to-production verification and deployment gating with unit tests, Playwright E2E, and Nick confirmation.

Official
Advanced
zzxtbetazzxtbeta

land-and-deploy

Merge pull requests, wait for CI, deploy, and verify canary health.

Community
Advanced
softwaresaltsoftwaresalt
1

pr-lifecycle

Manage pull request lifecycle from review through CI remediation and user-approved merge.

Community
Advanced