skills.rest
hdkz-dev
hdkz-devCOMMUNITY
Explore all skills by this author →
GitHub

pr-review-handler

Automate GitHub PR review workflows from feedback analysis to merge.

1|Updated Feb 6, 2026
Search Tags:#automation#workflow#github#merge#review#pr
One-click install
npx skills add https://github.com/hdkz-dev/multi-game-engines --skill pr-review-handler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-handler
Source: https://github.com/hdkz-dev/multi-game-engines/tree/main/.agent/skills/pr-review-handler
Command: npx skills add https://github.com/hdkz-dev/multi-game-engines --skill pr-review-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated end-to-end PR review workflow to ensure feedback is captured, fixes are applied, and merges only occur after all checks pass.

Core Features & Use Cases

  • Analyze feedback from PR comments and reviews to build a concrete task list.
  • Verify whether feedback items are addressed, and apply fixes across the codebase as needed.
  • Cross-check for similar issues to propagate fixes broadly and maintain consistency.
  • Run final verification: tests and lint, ensuring code quality before merge.
  • Merge PR automatically when mergeable and all checks pass, with safeguards.

Quick Start

Execute the pr-review-handler on a target PR to automatically analyze feedback, apply fixes, and merge when ready.

Frequently Asked Questions about pr-review-handler

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

FAQPage Schema
How do I automate GitHub PR review feedback from comments to merge?▼

Automating GitHub PR review involves analyzing comments to build a task list, applying fixes across the codebase, cross-checking for similar issues, and merging when all checks pass. This ensures feedback-driven changes are handled consistently before merge.

What is the best way to handle multiple reviewer feedback on a pull request?▼

Handling multiple reviewer feedback requires analyzing PR comments and reviews to construct a concrete task list. Fixes are then applied across the codebase, and similar issues are cross-checked to propagate updates broadly and maintain consistency before merging.

Can I automatically merge a GitHub PR only after tests and lint checks pass?▼

You can automatically merge a GitHub PR by running a final verification stage that validates tests and lint results. The PR merges only when it is mergeable and all validation checks pass, ensuring code quality with built-in safety safeguards.

How do I verify if PR review comments are addressed before merging code?▼

To verify PR review comments are addressed, analyze feedback to generate a task list, apply the necessary codebase fixes, and run explicit validation checks. A final verification stage confirms all feedback items are resolved before the automated merge.

Does automated PR review work for propagating fixes across similar codebase issues?▼

Automated PR review cross-checks for similar issues across the codebase to propagate fixes broadly. This ensures consistency by applying feedback-driven changes to all relevant areas before running final tests and merging the pull request.

Related Skills

Explore More Software Engineering Skills→
Luohao-YanLuohao-Yan
6

pr-comments

Fetch GitHub PR review comments from the current branch via GitHub API.

Community
Intermediate
open-horizon-labsopen-horizon-labs
3

ship

Coordinate merged code delivery through CI/CD pipelines and production readiness checks.

Official
Advanced
jmylchreestjmylchreest
15

verify

Run tests, type checks, linting, and builds across TypeScript, Go, and Python.

Community
Advanced
Codagent-AICodagent-AI
30

fix-pr

Resolve CI failures and review comments on GitHub pull requests.

Official
Advanced