skills.rest
doubleflannel
doubleflannelCOMMUNITY
Explore all skills by this author →
GitHub

accept-pr

Automate GitHub pull request finishing from review to merge.

Updated Aug 23, 2026
Search Tags:#git#workflow#changelog#github#merge#lint#pull-request
One-click install
npx skills add https://github.com/doubleflannel/12-30-test-codex-ip --skill accept-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accept-pr
Source: https://github.com/doubleflannel/12-30-test-codex-ip/tree/main/skills/accept-pr
Command: npx skills add https://github.com/doubleflannel/12-30-test-codex-ip --skill accept-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates finishing a GitHub pull request end-to-end from review to merge, including changelog updates, acknowledgments, lint, and post-merge cleanup.

Core Features & Use Cases

  • End-to-end PR guidance: manage review, apply fixes if needed, ensure changelog is updated, thank contributors, and merge back to main.
  • Guardrails & reliability: validates target branch, checks for a clean working tree, handles drafts, conflicts, and fork restrictions.
  • Workflow context: leverages GitHub CLI and standard repo tooling to operate within typical team or open-source workflows.

Quick Start

Provide a PR URL or number to begin the end-to-end merge flow.

Frequently Asked Questions about accept-pr

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

FAQPage Schema
How do I automate merging a GitHub pull request end-to-end?▼

Automating a GitHub pull request end-to-end involves validating the target branch, applying fixes, updating CHANGELOG.md, running repo lint checks, performing a rebase or merge, and cleaning up branches. This requires git and GitHub CLI to execute the workflow.

Can I use this workflow to update the changelog before merging a PR?▼

Yes, updating CHANGELOG.md is a built-in step of the PR merge workflow. It ensures changelog updates are enforced before the final rebase or merge occurs, keeping project records accurate.

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

Yes, GitHub CLI and git are required dependencies to automate pull request merges. The workflow leverages these tools to check PR readiness, handle conflicts, and perform the final merge back to the main branch.

What is the best way to handle draft PRs and branch conflicts during a merge?▼

Handling draft PRs and branch conflicts requires built-in guardrails that validate the target branch, check for a clean working tree, and manage draft statuses. The workflow notes these restrictions before attempting a rebase or merge on the main branch.

Why does my pull request workflow fail on forked repositories?▼

Pull request workflows enforce fork restrictions to maintain reliability. The workflow validates the target branch, checks for a clean working tree, and notes fork restrictions before proceeding, preventing unsafe merges from forked repositories.

Related Skills

Explore More Software Engineering Skills→
JoeCP17JoeCP17
8

pull-request

Draft an intent-focused GitHub pull request from the current git branch against main.

Community
Intermediate
lookatitudelookatitude
6

technical-writer-release-notes

Generate release notes and changelogs from merged PRs and issues.

Community
Advanced
liauw-medialiauw-media
3

git-workflow

Enforce atomic Git commits with pre-commit verification and standardized messages.

Community
Advanced
ksciuskscius
2

fix-merge-conflicts

Resolve Git merge conflicts and verify buildable, test-passing state.

Community
Advanced