Skill1.4k repo starsupdated 3d ago
merge-pr
Merge a pull request using gh pr merge --admin
Install in Claude Code
Copygit clone --depth 1 https://github.com/dyoshikawa/rulesync /tmp/merge-pr && cp -r /tmp/merge-pr/.rulesync/skills/merge-pr ~/.claude/skills/merge-prThen start a new Claude Code session; the skill loads automatically.
Definition
SKILL.md
# Merge Pull Request Merge a pull request using `gh pr merge --admin`. ## Input ``` the user's request ``` ## Step 1: Determine the Target PR Parse `the user's request` to identify the PR to merge: ### Case A: PR number or URL is provided - Extract the PR number from the argument - Examples: `123`, `#123`, `https://github.com/owner/repo/pull/123` ### Case B: No argument provided - Get the PR associated with the current branch: ```bash gh pr view --json number,title,state ``` ### Case C: Unable to determine the PR If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), **ask the user** to specify which PR to merge. ## Step 2: Verify the PR Before merging, confirm the PR details: ```bash gh pr view <pr_number> --json number,title,state,mergeable,author,baseRefName,headRefName ``` Check: 1. The PR state is `OPEN` 2. Display the PR title and number to the user for confirmation If the PR is not open or not mergeable, inform the user and stop. ## Step 3: Check GitHub Actions Workflow Status Verify that all CI checks have passed before merging: ```bash gh pr checks <pr_number> ``` Check: 1. All workflow checks show `pass` status 2. No checks are `pending` or `fail` If any checks have failed or are still running, inform the user and ask whether to: - Wait for pending checks to complete - Investigate failed checks before merging - Proceed with merge anyway (using `--admin` will bypass required checks) ## Step 4: Merge the PR Execute the merge command: ```bash gh pr merge <pr_number> --admin --merge ``` **Important**: Only merge ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to merge. ## Step 5: Comment on the PR After the merge succeeds, leave a thank-you comment mentioning the PR author: ```bash gh pr comment <pr_number> --body "@<author_login> Thank you!" ``` Use the `author.login` value obtained in Step 2 for the mention. ## Step 6: Report Result After merging: 1. Confirm the PR was successfully merged 2. Display the merged PR number and title ## Step 7: Clean Up Local Branch If the local branch exists, please clean up the local branch. Execute: ```bash git checkout main && git pull --prune && git branch -d <branch-name> ``` Where `<branch-name>` is the head branch name from Step 2 (e.g., `fix/rulesync-import-targets`).
More from this repository
create-issueSkill
>-
create-scrap-issueSkill
>-
draft-releaseSkill
Draft a new release of the project.
git-worktree-runnerSkill
>-
playwright-cliSkill
Automate browser interactions, test web pages and work with Playwright tests.
release-dry-runSkill
Dry run for release: summarize changes since last release and suggest version bump.
rulesync-feature-researchSkill
>-
security-scan-diffSkill
Scan for malicious code in git diff between a tag/commit and HEAD