skills.rest
nsollazzo
nsollazzoCOMMUNITY
Explore all skills by this author →
Website𝕏@n_sollazzoGitHub

merge-and-monitor

Merge a GitHub pull request, watch its deployment pipeline, and verify production health.

Updated Jun 15, 2026
Search Tags:#ci/cd#monitoring#pull request#deployment#github#merge#gh cli
One-click install
npx skills add https://github.com/nsollazzo/ship-kit --skill merge-and-monitor-nsollazzo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-and-monitor
Source: https://github.com/nsollazzo/ship-kit/tree/main/.agents/skills/merge-and-monitor
Command: npx skills add https://github.com/nsollazzo/ship-kit --skill merge-and-monitor-nsollazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR is only half the job — teams still need to confirm the deployment it triggers actually completes and that the live system stays healthy. This Skill automates that post-merge loop with evidence at every stage instead of blind assumptions. ## Core Features & Use Cases - Gated merge: Verifies the PR is approved, CI-green, and mergeable via the GitHub CLI before merging, and stops with a clear report if anything blocks. - Deployment tracking: Locates the workflow or external CD triggered by the merge, matches the run to the exact merge commit SHA, and watches it to completion. - Health verification: Reads the pipeline's own smoke-test output or invokes a verify step against the deployed surface, then reports concrete evidence. - Use Case: After a reviewer approves your PR, ask the agent to merge it and confirm the production deploy is healthy — it merges, watches the GitHub Actions deploy run, checks the live endpoint, and reports the run URL and health output. ## Quick Start Ask the agent to merge PR 42 and monitor the deployment until it is verified healthy.

Frequently Asked Questions about merge-and-monitor

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

FAQPage Schema
How do I merge a GitHub PR and monitor the deployment automatically?▼

Use the gh CLI to verify the PR is approved and CI-green, merge it with gh pr merge, then locate the deploy workflow triggered by the merge commit and watch it with gh run watch. This Skill automates that full sequence and reports evidence at each stage.

How to verify a deployment is healthy after merging a pull request?▼

First check whether the deploy workflow itself runs smoke tests and read their output as evidence. Otherwise exercise the deployed surface directly — the live URL or endpoint the change touches — rather than the local working copy.

Does this work with external CD tools like Vercel or ArgoCD?▼

Yes. If no GitHub Actions deploy workflow is found, the Skill checks the repo's documentation for external CD systems such as Vercel, Flux, or ArgoCD and monitors accordingly. If no deployment pipeline exists, it says so and stops.

What happens if the deployment fails after the merge?▼

A failed deploy is treated as an incident, not a stage to retry. The Skill fetches the failing log with gh run view --log-failed, reports it verbatim, and stops — rolling back or re-running is left to the user's decision.

Why does gh pr merge fail with a 401 or 403 error?▼

Some organization token setups reject the GraphQL merge path while accepting REST. The fallback is gh api -X PUT repos/{owner}/{repo}/pulls/<n>/merge with the desired merge method, which this Skill applies automatically.

Related Skills

Explore More Software Engineering Skills→
shawn-sandyshawn-sandy

merge

Verifies pull request readiness gates and merges approved PRs via GitHub CLI.

Community
Advanced
GreyborneGreyborne

aiception

Extract verified lessons from work sessions into reusable skills in Open Brain.

Community
Intermediate
srnnklssrnnkls

code-test

Enforce a test-first workflow requiring failing tests before implementation.

Community
Intermediate
SantiagoisperSantiagoisper

land-and-deploy

Merge pull requests, deploy code changes, and verify production readiness.

Community
Advanced