skills.rest
NSEvteev
NSEvteevCOMMUNITY
Explore all skills by this author →
GitHub

merge

Merge GitHub Pull Requests with pre/post checks and main synchronization.

31|5|Updated Jan 14, 2026
Search Tags:#git#github#cleanup#merge#pull-request#pre-checks
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill merge-nsevteev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/merge
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill merge-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge PRs with pre/post checks, synchronize main, and cleanup automatically to avoid manual mistakes.

Core Features & Use Cases

  • Pre/post-merge checks enforcement: ensure required checks pass before merging.
  • Main branch synchronization: update main after merge to reflect latest state.
  • Automatic cleanup: delete merged branches and tidy up related artifacts after merging.

Quick Start

Run /merge <PR-number> to merge a PR with pre/post checks and cleanup.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate a GitHub pull request merge with pre-checks?▼

To automate a GitHub pull request merge with pre-checks, use a command like /merge <PR-number>. This enforces required validation checks, synchronizes the main branch, and cleans up merged artifacts automatically.

Can I automatically delete merged branches after a PR merge?▼

Yes, you can automatically delete merged branches after a PR merge by using automated cleanup features. The process deletes merged branches and tidies up related artifacts to avoid manual mistakes and keep the repository clean.

What is the best way to keep the main branch up to date after merging?▼

The best way to keep the main branch up to date after merging is through main branch synchronization. This automated process updates main after a merge to reflect the latest state without requiring manual git pull commands.

Does the gh pr merge command support post-merge cleanup tasks?▼

Yes, the gh pr merge command supports post-merge cleanup tasks when automated. It applies to PR workflows requiring automated validation, cleanup of merge artifacts, and keeping the main branch synchronized with optional post-merge tasks.

Why do I need pre-merge and post-merge checks for pull requests?▼

You need pre-merge and post-merge checks for pull requests to ensure required validations pass before merging and to verify repository hygiene afterward. This enforcement avoids manual mistakes and guarantees safe merging of GitHub Pull Requests.

Related Skills

Explore More Software Engineering Skills→
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
Soul-Brews-StudioSoul-Brews-Studio
116

merged

Switch to main, pull latest changes, and delete merged branches.

Official
Basic
phillipganphillipgan
1

gh-issues

Automates GitHub issue management and pull request creation for CI workflows.

Community
Advanced
HorusGoulHorusGoul
8

land

Merge pull requests by resolving conflicts, checking CI/CD, and squashing via GitHub API.

Community
Advanced