review-and-merge

Drives a GitHub pull request through automated review rounds to a merged state.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/forhas/pure-dev --skill review-and-merge-forhas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-and-merge
Source: https://github.com/forhas/pure-dev/tree/main/plugins/notion-dev/skills/review-and-merge
Command: npx skills add https://github.com/forhas/pure-dev --skill review-and-merge-forhas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Merging a pull request requires resolving review comments, re-running code reviewers, waiting on CI, and verifying every thread is resolved — a slow, manual loop. This Skill automates that entire cycle: it resolves existing review feedback, loops the configured reviewer (Codex or Copilot) until no meaningful issues remain, falls back to a local fresh-agent review when the reviewer is unavailable, then merges and deletes the remote branch. ## Core Features & Use Cases - Automated review loop: Triggers and re-triggers Codex or Copilot reviews, triages findings with a judgment bar (absorb, file, drop, blocked), and applies only changes that genuinely improve the code. - Local fallback reviewer: When the configured reviewer hits quota, is not configured, errors, or stays silent, a local fresh-agent review loop takes over so the PR still reaches merge. - Convergence controls and merge gates: A findings ledger with severity ratcheting and induced-chain detection prevents endless fix cycles, while green-CI, thread-resolution, and acceptance-criteria gates guard the final merge. - Use Case: After /notion-dev:ticket finishes its build phase, run the review loop on the opened PR — it resolves reviewer findings across multiple rounds, waits out slow Copilot responses, and squash-merges once all gates pass. ## Quick Start Ask the assistant to review and merge pull request 42 using the configured reviewer, letting it resolve feedback and merge automatically.

Frequently Asked Questions about review-and-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically review and merge a GitHub pull request?

Invoke the skill with the PR number, for example "review and merge PR 42". It resolves existing review comments, loops the configured Codex or Copilot reviewer until no meaningful issues remain, verifies all gates, then merges and deletes the remote branch.

Codex vs Copilot reviewer for automated PR review loops?

Both are supported and configured via the reviewer key in .claude/notion-dev.config.json. Codex is triggered with an @codex review comment, while Copilot is triggered by requesting the copilot-pull-request-reviewer bot; the skill handles each one's response format and latency differences.

What happens when the code reviewer is unavailable or hits quota?

The skill detects quota messages, not-configured errors, and silence, then falls back to a local fresh-agent review loop that judges the diff against the PR title and body. The fallback runs its own round counter up to the configured reviewsCap.

Does the review loop require jq and the GitHub CLI?

Yes, both the gh CLI and the standalone jq binary must be on PATH. The skill pipes gh api output through jq for thread mapping and author filtering, and stops with install instructions if jq is missing.

Why does the review loop stop before merging my pull request?

The loop stops on explicit conditions: a closed or draft PR, failing CI checks, a dirty working tree, a timed-out reviewer wait, both review seats failing, or an unsatisfiable pre-merge check. Each stop produces a report explaining the cause.

Can the review loop run without pausing for user input?

Yes, pass --non-interactive to resolve all judgment calls autonomously and never pause. Decisions that would normally prompt the user are logged in the final report instead.