github-pr-merge

To automate GitHub PR merges safely, this Skill enforces pre-merge validations by verifying tests, lint, and CI status before executing the merge, ensuring your PR is only merged when all checks are green.

Yes, you can prevent merging a GitHub PR with unresolved comments. This Skill enforces reviewer readiness by verifying that no unreplied comments remain before proceeding with the merge.

The best way to safely merge a GitHub PR and delete the feature branch is using this Skill, which performs a safe merge using the preferred strategy and then handles post-merge cleanup by deleting the feature branch.

Yes, the automated PR merge process requires manual user confirmation. This Skill includes user confirmation as a pre-merge step to ensure you have final approval before the checks are validated and the merge is executed.

Your GitHub PR merge fails when checks are running because this Skill strictly enforces pre-merge checks, preventing the merge process if CI results are incomplete or checks fail to ensure safe merging.

Yes, you can use gh pr merge with --merge in an automated workflow. This Skill satisfies that functional requirement by using the command to complete the merge and subsequently cleaning up the feature branch.