Skills github-pr-merge
📦

github-pr-merge

Content revision r1 High Risk ⚙️ External commands

Merge GitHub Pull Requests Safely

Pull request merges need consistent validation before repository changes happen. This skill guides Claude, Codex, or Claude Code through checks, confirmation, merge, and cleanup.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "github-pr-merge" from https://skillstore.io/skills/bae-changhyun-github-pr-merge.md and its manifest at https://skillstore.io/api/skills/bae-changhyun-github-pr-merge/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/bae-changhyun-github-pr-merge.md Signed manifest GET /api/skills/bae-changhyun-github-pr-merge/manifest Signed lockfile GET /api/skills/bae-changhyun-github-pr-merge/lockfile

Test it

Using "github-pr-merge". Merge the current PR after checking it.

Expected outcome:

  • PR #42 is ready: tests passed, lint passed, CI is green, and review comments are answered.
  • Merge message drafted with key changes, review count, and test summary. Waiting for your confirmation before merge.

Using "github-pr-merge". Check whether this PR can merge.

Expected outcome:

The merge is blocked because two review comments have no replies. Run the review workflow before merging.

Using "github-pr-merge". After merge, clean up my branch.

Expected outcome:

The remote branch can be deleted during merge. Local branch cleanup should happen only after switching to the target branch and pulling updates.

Security Audit

High Risk
v8 • 7/6/2026 Open versioned report

The skill is a GitHub PR merge workflow that intentionally uses gh, git, and make commands. Most static hits are Markdown or read-only GitHub CLI checks, but merge, branch deletion, and repository-defined make targets are real risks. The frontmatter also contains prompt override wording that should be softened before marketplace publication.

1
Files scanned
185
Lines analyzed
9
Review items
0
False positives ignored

Confirmed security concerns (1)

High
SKILL.md:3
Prompt Injection Attempt Detected
The skill description says "MUST use this skill" and "OVERRIDES default PR merge behavior," which attempts to force agent routing and override normal behavior.
The wording directly uses mandatory activation and override language in the skill frontmatter. It does not ask to skip security review, but it can manipulate agent behavior.
Capability review items (9)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
SKILL.md:113-124
Ruby/shell backtick execution
```bash
The block instructs running gh pr merge with --delete-branch, which changes the GitHub repository and deletes the remote branch. The prior confirmation step reduces risk but does not remove the high-impact action.
High
SKILL.md:114-123
Shell command substitution
gh pr merge $PR --merge --delete-branch --body "$(cat <<'EOF'
This line is part of the gh pr merge command with --delete-branch. The heredoc body is quoted, but the surrounding command performs a repository write and branch deletion.
High
SKILL.md:113-124
Template literal with command substitution
```bash
The template wraps a gh pr merge command that writes to GitHub and deletes the remote branch. The command substitution forms the body safely but the operation remains high impact.
Medium
SKILL.md:12-32
Ruby/shell backtick execution
```bash
The quick start block includes external gh, make, and git commands that can merge a PR and delete branches. This is intended workflow behavior, but it has real repository impact if run in the wrong context.
Medium
SKILL.md:40-41
Ruby/shell backtick execution
| Tests passing | `make test` | Yes |
The inline make test command is a project-defined external command. It is legitimate validation, but running Makefile targets from an untrusted repository can execute arbitrary project code.
Medium
SKILL.md:41-42
Ruby/shell backtick execution
| Linting passing | `make lint` | Yes |
The inline make lint command is a project-defined external command. It is legitimate validation, but repository-controlled lint targets can execute arbitrary local scripts.
Medium
SKILL.md:77-86
Ruby/shell backtick execution
```bash
The validation block runs make test and make lint, which execute repository-defined commands. This is expected for PR validation but risky in untrusted workspaces.
Medium
SKILL.md:130-134
Ruby/shell backtick execution
```bash
The post-merge block runs git checkout, git pull, and git branch -d. These mutate the local workspace and delete a local branch, so they are real external-command risks.
Medium
SKILL.md:12-32
Template literal with command substitution
```bash
The quick start template includes command substitutions plus merge and cleanup commands. It is intended automation guidance, but it can alter GitHub and local git state.

Risk Factors

⚙️ External commands (32)
SKILL.md:12-32 SKILL.md:32-40 SKILL.md:40-41 SKILL.md:41-42 SKILL.md:42-50 SKILL.md:50-54 SKILL.md:54-58 SKILL.md:58-68 SKILL.md:68-77 SKILL.md:77-86 SKILL.md:86-92 SKILL.md:92-96 SKILL.md:96-101 SKILL.md:101-109 SKILL.md:109-113 SKILL.md:113-124 SKILL.md:124-126 SKILL.md:126-130 SKILL.md:130-134 SKILL.md:134-140 SKILL.md:140-148 SKILL.md:14 SKILL.md:15 SKILL.md:51 SKILL.md:52 SKILL.md:60 SKILL.md:63-64 SKILL.md:114-123 SKILL.md:12-32 SKILL.md:50-54 SKILL.md:58-68 SKILL.md:113-124
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/bae-changhyun-github-pr-merge/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/bae-changhyun-github-pr-merge/security.svg)](https://skillstore.io/skills/bae-changhyun-github-pr-merge?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/bae-changhyun-github-pr-merge?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bae-changhyun-github-pr-merge/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/bae-changhyun-github-pr-merge.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Bae-ChangHyun. (2026). github-pr-merge security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bae-changhyun-github-pr-merge/audits/8

BibTeX citation

@techreport{bae-changhyun-bae-changhyun-github-pr-merge-2026, author = {Bae-ChangHyun}, title = {github-pr-merge security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/bae-changhyun-github-pr-merge/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "github-pr-merge security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "Bae-ChangHyun" date-released: "2026-07-06" url: "https://skillstore.io/skills/bae-changhyun-github-pr-merge/audits/8" identifiers: - type: other value: "skillstore:bae-changhyun-github-pr-merge:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
71
Community
91
Spec Compliance

What You Can Build

Complete a reviewed feature merge

Validate checks, summarize readiness, and merge after explicit approval.

Verify review comments before merge

Check whether original review comments have replies before accepting a pull request.

Prepare an assistant-guided merge

Ask an AI coding assistant to collect status, draft the merge summary, and wait for approval.

Try These Prompts

Check the Current PR 
Check the current GitHub pull request. Run the required validation steps, summarize the results, and ask me before merging.
Verify Review Readiness 
Review the current PR for test, lint, CI, and comment status. Tell me whether anything blocks the merge.
Merge a Specific PR 
For PR #123, verify CI, tests, lint, and review comments. Prepare the merge body, then wait for my approval.
Merge and Clean Up 
Use the GitHub PR merge workflow for PR #123. Validate every gate, merge only after my confirmation, then prepare cleanup steps.

Best Practices

  • Confirm the PR number and repository before running any merge command.
  • Treat project validation commands as repository code and run them only in trusted workspaces.
  • Keep branch deletion as a separate decision when the branch is shared.

Avoid

  • Do not merge when tests, lint, CI, or review threads are unresolved.
  • Do not use the skill to bypass branch protection or reviewer approval.
  • Do not run merge commands from a fork or untrusted checkout without verifying context.

Frequently Asked Questions

Does this skill merge automatically?
No. It instructs the assistant to ask for explicit confirmation before merging.
What tools are required?
It requires GitHub CLI, git, authentication to the target repository, and the project validation commands.
Can it respond to review comments?
No. The workflow says to stop and use a review workflow when unreplied comments exist.
Does it support squash merges?
The skill recommends merge commits only. Adjust the workflow manually if project policy differs.
Why does it check comments?
It checks comment replies to reduce the chance of merging unresolved review feedback.
Is it safe for untrusted repositories?
Use caution. Project validation commands can execute repository-defined code on the local machine.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Bae-ChangHyun/cc-plugins-bch/tree/main/plugins/gitwf/skills/github-pr-merge

Ref

c4231f0153ccd2a2ed62274c5a372bf8f2386d3f

Maintenance freshness

7/18/2026

Usage

6 downloads · 234 views

File structure

📄 SKILL.md