skills.rest
bitpantry
bitpantryCOMMUNITY
Explore all skills by this author →
GitHub

finish-pr

Merge reviewed GitHub pull requests after tests pass and branches sync.

Updated Sep 18, 2020
Search Tags:#pull request#CI/CD#GitHub#merge#review
One-click install
npx skills add https://github.com/bitpantry/BitPantry.CommandLine --skill finish-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-pr
Source: https://github.com/bitpantry/BitPantry.CommandLine/tree/main/.github/skills/finish-pr
Command: npx skills add https://github.com/bitpantry/BitPantry.CommandLine --skill finish-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the merging of GitHub pull requests after review and completion, automating the process and ensuring quality control.

Core Features & Use Cases

  • Automated Pull Request Merging: Merges pull requests that have been reviewed and approved, reducing manual effort.
  • Review Feedback Integration: Integrates with GitHub reviews to ensure all feedback has been addressed before merging.
  • Branch Synchronization: Ensures the pull request branch is up to date with the base branch before merging.
  • Full Test Suite Execution: Runs the project's full test suite to ensure code quality before merging.
  • Issue Closure: Automatically closes linked issues upon successful merge.
  • Use Case: Ideal for teams that want to streamline their pull request workflow, ensuring code quality and reducing manual merges.

Quick Start

Use the finish-pr skill to merge pull request number 42 after it has been reviewed and approved.

Frequently Asked Questions about finish-pr

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

FAQPage Schema
How do I automate merging a GitHub pull request after review?▼

Automating a GitHub pull request merge requires synchronizing branches, verifying review feedback is addressed, and running the full test suite before execution. This skill uses GitHub CLI to manage that workflow automatically.

What's the best way to ensure branches are synchronized before a pull request merge?▼

To ensure branches are synchronized before a pull request merge, you need to verify the pull request branch matches the base branch. This skill checks branch synchronization and runs the full test suite prior to merging.

Do I need the GitHub CLI to automate pull request merges?▼

Yes, you need the GitHub CLI (gh) installed and configured with repository access to automate pull request merges. The tool relies on gh to validate reviews, synchronize branches, and execute the final merge.

Can I automatically close linked GitHub issues when a pull request is merged?▼

Yes, you can automatically close linked GitHub issues upon a successful pull request merge. This skill manages the merge process and handles linked issue closure automatically after tests pass.

How does review feedback integration work before merging a pull request?▼

Review feedback integration works by checking GitHub reviews to ensure all comments and requested changes are addressed. The pull request is only merged after this validation confirms the feedback is fully resolved.

Related Skills

Explore More Software Engineering Skills→
auldsyababuaauldsyababua
6

pr-backlog-cleaner

Triage, rebase, and verify GitHub pull requests for safe disposition.

Community
Advanced
JacobPEvansJacobPEvans
3

refresh-repo

Synchronize a local Git repository and check open Pull Requests for merge readiness.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate
zhaow-dezhaow-de

merge-pr

Merge reviewed GitHub pull requests with a merge commit.

Community
Intermediate