schedule-merge-review

Reviews open GitHub pull requests and posts one findings comment with a merge verdict per head commit.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-merge-review-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-merge-review
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-merge-review
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-merge-review-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests often sit unreviewed for days, forcing whoever decides to merge to start from a cold diff. This Skill runs unattended on a schedule, reviews every open pull request waiting on a reviewer, and posts findings with a merge verdict so a human starts from analysis rather than raw changes. ## Core Features & Use Cases - Automated Diff Review: Runs a structured code-review checklist over each pull request diff, classifying findings as Blocking, Important, or Suggestion with file and line references. - Merge-State Analysis: Reads checks, mergeable status, distance from the base branch, and linked issues to produce one verdict per pull request: ready, changes requested, or blocked. - Idempotent Commenting: Posts exactly one comment per head commit using a hidden marker, so daily re-runs only review what changed and never flood a thread. - Use Case: A team schedules a weekday run so every pull request pushed the previous day already carries a review comment with findings and a verdict when reviewers arrive in the morning. ## Quick Start Run the schedule-merge-review skill against this repository to review all open pull requests and post a findings comment with a merge verdict on each one.

Frequently Asked Questions about schedule-merge-review

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

FAQPage Schema
How do I automatically review open GitHub pull requests on a schedule?▼

Run this skill on a daily schedule with an authenticated gh CLI session. It lists open pull requests, runs a code-review checklist over each diff, checks merge state, and posts one findings comment with a verdict per pull request.

Can an automated review approve or merge pull requests?▼

No. This skill never calls gh pr review --approve, never requests changes formally, never merges, and never pushes. It writes exactly one thing: a comment with findings and a verdict, leaving approval and merging to a person.

Does re-running a scheduled pull request review post duplicate comments?▼

No. Each comment carries a hidden marker keyed to the pull request head commit. A pull request whose head already has the marker is skipped, so re-running costs one list call and never floods a thread.

What verdicts does an automated merge review produce?▼

Each pull request gets one of three verdicts: ready when there are no blocking findings and checks are green, changes requested when at least one blocking finding exists, and blocked when checks fail, conflicts exist, or the branch is behind base.

What are the limitations of unattended pull request review?▼

It reports findings but cannot fix them; the attended counterpart pr-merge-ready handles fixes. It also caps reviews per run (default 10, oldest first) and skips drafts unless explicitly included.