review-pr

To automate pull request reviews in GitHub workflows, you can use a Skill that checks out an open PR, applies fixes, and posts a verdict comment to communicate merge or close decisions. It requires gh CLI access and repository permissions to push commits.

A maintainer-style PR review workflow automates triage by checking out a PR, applying deterministic fixes, pushing changes back to the branch, and posting a structured verdict comment. This enables clear merge-or-close decisions with minimal manual steps.

Yes, you need gh CLI access to automate PR fixes and comments. The workflow requires a configured repository context and permissions to read PR metadata, diffs, and checks, as well as push commits or comments back to the PR branch.

You apply fixes and push commits to a PR branch automatically by running a review workflow that checks out the PR, applies deterministic fixes, and pushes the changes back to the branch using configured repository permissions.

Yes, you can review the latest open pull request without providing a PR number. You can omit the PR number to use the latest open PR automatically, enabling quick triage and fast fixes for the most recent submission.

Limitations of automating PR triage and merge decisions include requiring explicit permissions to read PR metadata, diffs, and checks, as well as push commits or comments. It is designed for open pull requests in GitHub workflows and needs a configured repository context.