skills.rest
bkelly-lab
bkelly-labOFFICIAL
Explore all skills by this author →
GitHub

approve-pr

Automate GitHub PR pre-flight checks, approval, and squash-merge with branch deletion.

50|17|Updated Sep 2, 2023
Search Tags:#automation#github#merge#pr#preflight#pull-request
One-click install
npx skills add https://github.com/bkelly-lab/jkp-data --skill approve-pr-bkelly-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: approve-pr
Source: https://github.com/bkelly-lab/jkp-data/tree/main/.claude/skills/approve-pr
Command: npx skills add https://github.com/bkelly-lab/jkp-data --skill approve-pr-bkelly-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pre-flight checks and safe merge operations for GitHub pull requests, ensuring only validated PRs are merged.

Core Features & Use Cases

  • Pre-flight checks: verify CI status, conflicts, and reviews before merging.
  • Merge automation: perform squash-merge and delete branch after approval.
  • Use Case: Maintainers of open-source or enterprise repos can enforce safer PR workflows with minimal manual steps.

Quick Start

Provide the PR number or ensure you are on the PR branch, then run the skill to perform pre-flight checks and squash-merge the PR.

Frequently Asked Questions about approve-pr

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

FAQPage Schema
How do I automate GitHub pull request merge and pre-flight checks?▼

You can automate GitHub pull request merge and pre-flight checks by using a skill that validates CI status, conflicts, and reviews before performing a safe squash-merge and deleting the branch.

What are PR pre-flight checks and why are they needed before merging?▼

PR pre-flight checks verify CI status, unresolved conflicts, and required reviews before merging, ensuring only validated pull requests are merged into your repository branches safely.

Do I need gh CLI to automate squash-merge on GitHub pull requests?▼

Yes, automating squash-merge on GitHub pull requests requires gh CLI access and active network connectivity to verify the PR state and perform the branch deletion.

Can I use PR merge automation for enterprise GitHub repositories?▼

Yes, PR merge automation applies to both open-source and enterprise GitHub repositories to enforce safer PR workflows with minimal manual steps for maintainers.

What's the best way to enforce safe PR workflows with minimal manual steps?▼

The best way to enforce safe PR workflows is automating pre-flight checks, approval, and squash-merging to guarantee only validated pull requests are merged into your codebase.

Why does automated PR merging fail when there are unresolved conflicts?▼

Automated PR merging fails on unresolved conflicts because the pre-flight checks detect them during state verification, halting the squash-merge to prevent corrupting the branch.

Related Skills

Explore More Software Engineering Skills→
vm0-aivm0-ai
76

github-automation

Automate GitHub repository, issue, PR, release, and workflow operations via gh CLI.

Official
Advanced
sakurosakuro
2

merge-pr

Merge GitHub pull requests with the gh CLI after validating CI checks and approvals.

Community
Intermediate
takemo101takemo101

ci-workflow

Automate post-PR workflows by monitoring CI checks, fixing failures, and merging.

Community
Advanced
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate