merge-pr

The merge-pr skill is designed to streamline and safeguard the process of merging GitHub pull requests using the `gh` CLI. It addresses the common challenge of ensuring that code changes are integrated safely into the main branch while adhering to best practices for code review, CI checks, and merge strategies. By providing structured guidance for pre-merge verification, merge execution, and post-merge updates, this skill reduces the risk of introducing errors or conflicts in the repository, making the merge process more reliable and efficient.

This skill offers a comprehensive set of features to support developers in managing pull requests. It includes pre-merge checks to confirm that all required CI tests have passed, approvals are in place, and no unresolved review comments remain. Users can select from multiple merge strategies—merge commit, squash merge, or rebase merge—based on the nature of the pull request and repository workflow. Additionally, it guides users on respecting repository branch deletion settings and ensures local branches are updated after a merge. The skill emphasizes using custom merge commit messages to maintain clear and consistent project history.

The merge-pr skill is particularly useful for developers, code reviewers, and DevOps engineers who regularly interact with GitHub repositories. It is ideal for teams that want to enforce consistent merging practices, maintain high-quality codebases, and reduce errors from manual merges. This skill can be leveraged in scenarios such as merging feature branches, completing code reviews, or maintaining CI/CD pipelines. By following its structured workflow, users can confidently manage pull requests while keeping local and remote repositories in sync.