merge-pr

Merge the current/previewed pull request (PR) after validating that all tasks are done, optionally respecting flags such as --no-edit and --delete-branch-if-only-stdin-and-no-open-issues, though these specifics are optional and depend on your chosen wording. Actually, simplest phrasing: merge the PR and optionally prune the git-tracking branch if it exists, else leave it unchanged.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vulnetix/vdb-api --skill merge-pr-vulnetix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/Vulnetix/vdb-api/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/Vulnetix/vdb-api --skill merge-pr-vulnetix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating pull requests with session todos, merging them if complete, or commenting with remaining tasks, significantly reducing manual oversight for code reviews.

Core Features & Use Cases

  • Automated PR Updates: Appends session todos to the PR description.
  • Conditional Merging: Merges PRs automatically when all tasks are completed.
  • Intelligent Commenting: Leaves a comment detailing remaining tasks if the PR is not yet complete.
  • Local Cleanup: Switches to the main branch, pulls latest changes, and deletes the feature branch after a successful merge.
  • Use Case: After completing a set of coding tasks for a feature, run this skill to automatically update the associated pull request, get it approved if all tasks are done, and merge it, or get feedback on what's left to do.

Quick Start

Run the merge-pr skill to update the current pull request with session todos and merge if complete.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate pull request merging based on completed tasks?

Automating pull request merging evaluates session todos and conditionally merges GitHub pull requests upon completion. It appends session todos to the PR description and merges automatically when all tasks are done.

What happens to a GitHub pull request when coding tasks are incomplete?

When coding tasks are incomplete, the pull request receives an intelligent comment detailing remaining tasks instead of merging. This prevents premature merges and provides clear feedback on outstanding work.

Do I need the GitHub CLI to automate branch management and PR updates?

Yes, you need the GitHub CLI (gh) to automate PR updates and manage branch states. The skill integrates with gh to manage pull request reviews, comments, and conditional merging.

How does local git branch cleanup work after a successful pull request merge?

Local git branch cleanup switches to the main branch, pulls latest changes, and deletes the feature branch after a successful merge. This automates local repository synchronization and removes obsolete feature branches.

Can I update a PR description automatically with my session todos?

Yes, you can update a PR description automatically by appending session todos directly to the pull request. This provides a live record of completed and outstanding coding tasks within the GitHub PR.

What is the best way to streamline developer workflow for code reviews?

Streamlining developer workflow for code reviews involves automating PR state management, conditional merging, and intelligent commenting. This reduces manual oversight by syncing session todos with GitHub pull requests automatically.