git-pr-merge

Audit and merge pull requests into the main branch via GitHub CLI.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/mattg101/SolidLink --skill git-pr-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr-merge
Source: https://github.com/mattg101/SolidLink/tree/main/docs/dev/.agent/skills/git-pr-merge
Command: npx skills add https://github.com/mattg101/SolidLink --skill git-pr-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of merging approved pull requests into the main branch and synchronizing the local development environment, ensuring code quality and up-to-date repositories.

Core Features & Use Cases

  • Automated PR Auditing: Inspects pull request changes for compliance.
  • Controlled Merging: Merges reviewed PRs into the main branch using GitHub CLI.
  • Local Environment Synchronization: Updates the local dev branch with changes from main.
  • Use Case: After a code review is complete and the PR is approved, use this skill to automatically merge it into the main branch and then update your local dev branch to reflect these changes.

Quick Start

Use the git-pr-merge skill to audit and merge pull request with ID 123.

Frequently Asked Questions about git-pr-merge

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

FAQPage Schema
How do I merge a pull request and sync my local dev branch?

Merging a pull request and syncing your local dev branch involves integrating the approved feature branch into main and updating the local environment to reflect the changes. This skill automates that process using GitHub CLI after auditing the PR.

Can I audit pull request changes for compliance before merging?

Auditing pull request changes for compliance before merging is supported by this skill. It inspects PR changes to ensure code quality and controlled integration into the main codebase before synchronizing your local environment.

Does this PR merging approach require the GitHub CLI?

This PR merging approach requires the GitHub CLI. You need the 'gh' tool installed to merge reviewed pull requests into the main branch and synchronize your local development environment.

What is the best way to automate code integration for feature branches?

Automating code integration for feature branches is best handled by a controlled workflow that audits and merges approved PRs into the main codebase. This ensures repository consistency and automated branch management without manual errors.

Why sync the local development branch after merging into main?

Syncing the local development branch after merging into main ensures repository consistency and keeps your local environment up-to-date with the latest integrated codebase changes, preventing future branch divergence.