accept-pr

majiayu000's avatarfrom majiayu000

Land one PR end-to-end (changelog + thanks, lint, merge, back to main).

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026
[CI and CD]

When & Why to Use This Skill

This Claude skill automates the entire Pull Request lifecycle, from initial checkout and local testing to changelog documentation and final merging. It solves the problem of manual, error-prone PR management by enforcing guardrails, ensuring linting compliance, and maintaining a clean repository state, significantly reducing the cognitive load on maintainers.

Use Cases

  • Open-Source Maintenance: Automatically thanking contributors and updating the CHANGELOG.md with proper PR references and credits during the merge process.
  • Workflow Standardization: Enforcing consistent merge strategies (like rebase) and ensuring that no PR is landed without passing local linting and status checks.
  • Developer Productivity: Streamlining the repetitive 'git checkout, pull, lint, merge, delete branch' cycle into a single command to keep the local environment and main branch in sync.
  • Quality Assurance: Acting as a local CI gatekeeper by running repository-specific linters and tests before code is pushed to the default branch.
nameaccept-pr
descriptionLand one PR end-to-end (changelog + thanks, lint, merge, back to main).

Accept PR

Input: PR number or URL (required). Default merge mode: rebase.

  1. Guardrails
  • Must end on main (or repo default branch if no main).
  • git status -sb clean before/after. No uncommitted changes.
  • If PR is draft, has conflicts, or base branch != main: stop + ask.
  • If PR is from a fork and you can’t push: stop + ask.
  1. Capture context
  • START_BRANCH="$(git branch --show-current)"
  • gh pr view <PR> --json number,title,author,baseRefName,headRefName,isDraft,mergeable,maintainerCanModify
  • Skim: gh pr view <PR> --comments and gh pr diff <PR>
  1. Checkout + suggested fixes
  • gh pr checkout <PR>
  • Apply fixes (and tests if needed). Keep edits minimal; follow repo conventions.
  • Ensure change/feature/regression is well-tested. If no tests exist, do the manual checks the repo expects and note it.
  • Commit with explicit paths (no git add .), then push: git push origin HEAD
  1. Changelog (and thank contributor)
  • Edit CHANGELOG.md (or project changelog file).
  • Add entry under the top “Unreleased”/latest section (match existing style).
  • Include PR + thanks, e.g.: - <short change> (#<num>) — thanks @<author>
  • Commit + push changelog if it changed.
  1. Lint
  • Run repo linter/gate (prefer existing scripts; fix until green).
  • If there’s no obvious lint target, search: rg -n "lint|biome|eslint|swiftlint|ruff" package.json Makefile scripts -S
  1. Merge (then delete PR branch)
  • Prefer rebase merge: gh pr merge <PR> --rebase --delete-branch
  • If rebase is disallowed, fallback to repo preference (--merge or --squash).
  1. Sync main + exit clean
  • git checkout main || git checkout "$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')"
  • git pull --ff-only
  • Verify merged: gh pr view <PR> --json mergedAt,mergeCommit
  • git status -sb (clean) + ensure you’re on main.