How do I install the Review Merge skill?

Run npx skillmds@latest add tarangdeep-goel-by/review-merge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review Merge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review Merge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review Merge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review Merge?

tarangdeep-goel-by (@tarangdeep-goel-by) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review Merge by tarangdeep-goel-by — Agent Skill

Name: Review Merge
Author: tarangdeep-goel-by

Review Merge

Review a PR AND merge it if it passes — find the current branch's PR, assess it against a quality rubric (correctness/tests/clean/style/scope), then `gh pr merge --squash --delete-branch`. Use when the user says /review-merge, 'review and merge this PR', 'ship this PR', or asks to merge a pull request. Distinct from /review (review-only, no merge) — review-merge is the merge moment. Use `--no-merge` for review-only.

File contents

Review & Merge PR

Review an open PR, assess code quality, and merge if it passes review.

Trigger

User says /review-merge optionally followed by a PR number or URL.

Process

1. Find the PR

If a PR number or URL is provided, use that
Otherwise, find the open PR for the current branch: gh pr list --head $(git branch --show-current) --json number,title,url
If no PR found, check for any open PRs in the repo: gh pr list --json number,title,url
If multiple PRs, ask the user which one

2. Review the PR

Run these in parallel:

gh pr view <number> --json title,body,state,additions,deletions,changedFiles,files
gh pr diff <number>
gh pr checks <number> (if CI exists)

3. Assess Quality

Evaluate the diff against these criteria:

Correctness: Does the code do what the PR title/description says?
Tests: Are there tests? Do they cover the key behaviors?
No junk: No debug logs, commented-out code, scaffold files, or credentials
Style: Follows existing patterns in the codebase
Scope: Changes are focused — no unrelated modifications

4. Report

Present a concise verdict:

PR #N: <title>
Files: N changed (+additions/-deletions)
<1-3 line summary of what it does>

✓ Correctness — <brief>
✓ Tests — <brief>
✓ Clean — <brief>
[or ✗ with explanation for any failures]

Verdict: MERGE / NEEDS FIXES

5. Act

If MERGE: Run gh pr merge <number> --squash --delete-branch
If NEEDS FIXES: List specific issues. Do NOT merge. Ask user if they want you to fix the issues.

Options

/review-merge — find and review current branch's PR
/review-merge 42 — review PR #42
/review-merge --no-merge — review only, don't merge even if passing

---name: review-mergedescription: Review a PR AND merge it if it passes — find the current branch's PR, assess it against a quality rubric (correctness/tests/clean/style/scope), then `gh pr merge --squash --delete-branch`. Use when the user says /review-merge, 'review and merge this PR', 'ship this PR', or asks to merge a pull request. Distinct from /review (review-only, no merge) — review-merge is the merge moment. Use `--no-merge` for review-only.---# Review & Merge PRReview an open PR, assess code quality, and merge if it passes review.## TriggerUser says `/review-merge` optionally followed by a PR number or URL.## Process### 1. Find the PR- If a PR number or URL is provided, use that- Otherwise, find the open PR for the current branch: `gh pr list --head $(git branch --show-current) --json number,title,url`- If no PR found, check for any open PRs in the repo: `gh pr list --json number,title,url`- If multiple PRs, ask the user which one### 2. Review the PRRun these in parallel:- `gh pr view <number> --json title,body,state,additions,deletions,changedFiles,files`- `gh pr diff <number>`- `gh pr checks <number>` (if CI exists)### 3. Assess QualityEvaluate the diff against these criteria:- **Correctness**: Does the code do what the PR title/description says?- **Tests**: Are there tests? Do they cover the key behaviors?- **No junk**: No debug logs, commented-out code, scaffold files, or credentials- **Style**: Follows existing patterns in the codebase- **Scope**: Changes are focused — no unrelated modifications### 4. ReportPresent a concise verdict:```PR #N: <title>Files: N changed (+additions/-deletions)<1-3 line summary of what it does>✓ Correctness — <brief>✓ Tests — <brief>✓ Clean — <brief>[or ✗ with explanation for any failures]Verdict: MERGE / NEEDS FIXES```### 5. Act- **If MERGE**: Run `gh pr merge <number> --squash --delete-branch`- **If NEEDS FIXES**: List specific issues. Do NOT merge. Ask user if they want you to fix the issues.## Options- `/review-merge` — find and review current branch's PR- `/review-merge 42` — review PR #42- `/review-merge --no-merge` — review only, don't merge even if passing

Frequently asked questions