Source profileQuality 72/100Review permissions
dyoshikawa/rulesync/.rulesync/skills/merge-pr/SKILL.md
merge-pr
Merge a pull request using gh pr merge --admin
- Source repository stars
- 1,263
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Merge a pull request using gh pr merge --admin.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/merge-pr"Safe inspection promptEditorial
Inspect the Agent Skill "merge-pr" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/merge-pr/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Step 1: Determine the Target PR
Parse the user's request to identify the PR to merge:
Extract the PR number from the argumentExamples: 123, 123, https://github.com/owner/repo/pull/123Get the PR associated with the current branch: - 02
Step 2: Verify the PR
Before merging, confirm the PR details:
The PR state is OPENDisplay the PR title and number to the user for confirmationBefore merging, confirm the PR details: - 03
Step 3: Check GitHub Actions Workflow Status
Verify that all CI checks have passed before merging:
All workflow checks show pass statusNo checks are pending or failWait for pending checks to complete - 04
Step 4: Merge the PR
Execute the merge command:
Execute the merge command:Important: Only merge ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to merge.
Permission review
Static risk signals and limitations
Runs scripts
The documentation asks the agent to run terminal commands or scripts.
Execute the merge command:Runs scripts
The documentation asks the agent to run terminal commands or scripts.
git checkout main && git pull --prune && git branch -d <branch-name>Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 72/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 1,263 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- dyoshikawa/rulesync
- Skill path
- .rulesync/skills/merge-pr/SKILL.md
- Commit
- 310b711fbe8cffc14debb276ade8a384c2b89083
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original 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:
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:
gh pr view <pr_number> --json number,title,state,mergeable,author,baseRefName,headRefName
Check:
- The PR state is
OPEN - 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:
gh pr checks <pr_number>
Check:
- All workflow checks show
passstatus - No checks are
pendingorfail
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
--adminwill bypass required checks)
Step 4: Merge the PR
Execute the merge command:
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:
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:
- Confirm the PR was successfully merged
- 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:
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).
Alternatives
Compare before choosing
Computed 8610,762
Jeffallan/claude-skills
code-reviewer
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quali
Computed 85234,327
affaan-m/ECC
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Computed 84933
dpearson2699/swift-ios-skills
swiftui-performance
Profile, diagnose, and remediate SwiftUI runtime performance using code review, Instruments, and repeatable measurements. Use when a SwiftUI screen renders slowly, scrolling or animations hitch, view bodies update excessively, list identity churns, layout work spikes, or broad Observation dependencies raise CPU cost. Covers evidence-based triage, SwiftUI Instruments lanes, lazy-container guardrails, state lifetime, and before/after verification.
Computed 83234,327
affaan-m/ECC
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.