merge-review

Automate PR review and merge workflows across WRFCoin repositories.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/tonykoop/claude-skills --skill merge-review-tonykoop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-review
Source: https://github.com/tonykoop/claude-skills/tree/main/plugins/coding/skills/merge-review
Command: npx skills add https://github.com/tonykoop/claude-skills --skill merge-review-tonykoop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR reviews and merges across WRFCoin repos are repetitive and time-consuming, leading to delays and potential inconsistencies.

Core Features & Use Cases

  • Automated PR review gathering: reads PR details, linked issues, and CI status.
  • Structured review comments and decisions: posts findings and merges or requests changes.
  • Cross-repo automation: coordinates actions across multiple WRFCoin repositories.

Quick Start

Tell the agent to start reviewing PRs across WRFCoin repositories and disable any non-essential checks until a merge decision is made.

Frequently Asked Questions about merge-review

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

FAQPage Schema
How do I automate GitHub pull request reviews and merges across multiple repositories?

Automating GitHub pull request reviews and merges across multiple repositories involves reading linked issues, inspecting diffs, and validating CI status to post structured comments before merging or requesting changes. This Skill coordinates those actions across WRFCoin repositories using GitHub CLI automation.

Can I validate CI status before merging a pull request automatically?

Yes, validating CI status before merging a pull request automatically is a core function of this workflow. It inspects CI pipeline results as part of the review process to ensure all checks pass before posting a merge decision or requesting changes.

What is the process for linking GitHub issues to automated PR review decisions?

Linking GitHub issues to automated PR review decisions requires reading the linked issue context alongside the PR diff and CI status. The automation uses this combined context to post structured review comments and determine whether to merge or request changes.

Does automated PR merging work across multiple WRFCoin repositories at once?

Yes, automated PR merging works across multiple WRFCoin repositories simultaneously by coordinating review actions across repos. It relies on consistent repository permissions and GitHub CLI automation to handle reviews and merges safely.

What permissions do I need to automate pull request merges with GitHub CLI?

Automating pull request merges with GitHub CLI requires explicit repository permissions to read PR details, post review comments, and execute merges. Proper write access must be configured across the targeted WRFCoin repositories for safe operation.

When should I disable non-essential checks during an automated PR review?

You should disable non-essential checks during an automated PR review when starting the workflow across repositories to prevent conflicting signals before a merge decision is made. This ensures the automation focuses on critical CI status and diff validation.