review

Poll GitHub pull requests to manage review cycles and merge approved changes.

3|1|Updated Feb 18, 2026

Search Tags:#automation #workflow #polling #code-review #pull-requests #buehler

Ready to run

npx skills add https://github.com/corrigantj/buehler --skill review-corrigantj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/corrigantj/buehler/tree/main/skills/review
Command: npx skills add https://github.com/corrigantj/buehler --skill review-corrigantj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After dispatch agents create task PRs, reviews must be coordinated and merged only with human approvals. The review skill polls for human review activity, routes feedback through the process, and ensures merged PRs reflect approved changes while capturing lessons learned.

Core Features & Use Cases

Polling for review activity: scans open task PRs on the feature branch to detect new reviews or comments.
Feedback routing & merging: directs outcomes to appropriate steps, performs merges when approved, and updates related issues.
Governance & learning: enforces CODEOWNERS gates and logs lessons learned with token calibration to inform future cycles.

Quick Start

Describe a dispatched feature and let the skill start polling for human reviews, coordinate feedback, and merge on approval.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate pull request review polling for GitHub task PRs?▼

Polling for human review activity works by continuously scanning open task PRs targeting a feature branch to detect new reviews or comments. This skill monitors GitHub PRs and routes outcomes to merge, wait, or comment steps based on detected feedback.

What's the best way to coordinate code review feedback routing after dispatch agents create PRs?▼

Code review feedback routing directs review outcomes to appropriate steps, performs merges when human approvals are detected, and updates related GitHub issues. This skill enforces CODEOWNERS gates and logs lessons learned with token calibration to inform future PR review cycles.

Do I need GitHub MCP and gh CLI to manage automated PR review cycles?▼

Yes, managing automated PR review cycles requires access to the repository via GitHub MCP and the gh CLI. You also need a configured review section in .github/buehler.yaml to define the polling and merging process for task PRs.

Can I enforce CODEOWNERS gates when merging automated pull requests?▼

Yes, you can enforce CODEOWNERS gates during the pull request merge process. This skill checks CODEOWNERS approvals before performing merges on task PRs, ensuring only human-approved changes are merged while capturing lessons learned for future token calibration.

How does token calibration work with GitHub pull request review automation?▼

Token calibration logs lessons learned from completed pull request review cycles to inform future automation runs. This skill captures review feedback and merge outcomes from task PRs, using the data to calibrate token usage and improve subsequent dispatch agent workflows.

Why are my task PRs waiting instead of merging after human review approval?▼

Task PRs may wait if human review approvals are not yet detected or CODEOWNERS gates are unmet. This skill polls open PRs and routes outcomes to wait, comment, or merge steps, only performing merges when explicit human approvals are confirmed on the feature branch.