Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
The github-pr-merge skill provides an automated solution for merging GitHub Pull Requests (PRs) after performing a thorough pre-merge validation checklist. This skill addresses the common challenges developers face when merging PRs, ensuring that code quality is maintained and all necessary checks are completed before a merge is executed. By automating this process, it reduces the risk of human error and allows developers to focus on more critical tasks in their workflow.
Key features of this skill include running a comprehensive pre-merge validation that checks passing tests, linting, CI status, and ensuring all comments have been addressed. It also confirms with the user before proceeding with the merge, providing a summary of the PR and any relevant details. Additionally, the skill handles post-merge cleanup tasks, making it easier for developers to maintain a clean and organized codebase without needing to manually delete branches or switch contexts.
This skill is particularly useful for development teams using GitHub who want to enforce best practices in their code review process. It targets developers, team leads, and project managers who are responsible for maintaining code quality and ensuring smooth collaboration in software development. By integrating this skill into their workflow, teams can streamline their PR merging process, improve code quality, and save time on repetitive tasks.
It automates the process of merging GitHub Pull Requests after validating a pre-merge checklist.
The skill checks for passing tests, linting, CI status, and ensures all comments have been replied to.
Yes, it requires the GitHub CLI and a proper setup of the project with necessary scripts for testing and linting.
Yes, as long as the repository is accessible through the GitHub CLI and adheres to the expected project structure.
The merge process will stop, and the user will be informed about the unreplied comments that need attention.
Quick Setup:
.claude/skills/Repository
fvadicamo/dev-agent-skills