pr-reviewer

Fetch pull request review comments, apply fixes, commit, and push follow-up updates.

286|24|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill pr-reviewer-fu-jie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/Fu-Jie/openwebui-extensions/tree/main/.gemini/skills/pr-reviewer
Command: npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill pr-reviewer-fu-jie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetches PR review comments and transforms them into actionable fixes.

Core Features & Use Cases

  • Fetches all review comments and distinguishes between inline and general feedback
  • Applies fixes locally, commits them, and pushes a follow-up update to advance the PR toward merge
  • Generates a concise follow-up message summarizing changes for the reviewer

Quick Start

Run the pr-reviewer workflow on your checked-out PR branch to fetch comments, apply fixes, commit them, and push for follow-up review.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I automatically apply fixes from GitHub PR review comments?

To automatically apply fixes from GitHub PR review comments, you can run an automation workflow on your checked-out branch that fetches inline and general feedback, applies the changes locally, commits them, and pushes a follow-up update to the pull request.

What is the best way to automate a pull request feedback loop up to merge?

Automating a pull request feedback loop involves fetching reviewer comments, transforming them into actionable code fixes, committing the changes, and pushing a follow-up update with a concise summary message to advance the PR toward merge.

Do I need the GitHub CLI and a local git branch to automate PR reviews?

Yes, automating PR reviews requires a configured git repository, authenticated GitHub CLI, and a local branch matching the PR head to ensure safe, deterministic operations when fetching comments and pushing follow-up commits.

Can I distinguish between inline code feedback and general PR comments when automating fixes?

Yes, the automation process fetches all review comments and distinguishes between inline code feedback and general pull request comments, transforming both into actionable local fixes before committing and pushing the updates.

How does the reviewer get notified after automated PR fixes are pushed?

After automated PR fixes are committed and pushed, the workflow generates a concise follow-up message summarizing the applied changes, closing the feedback loop and notifying the reviewer that updates are ready for re-evaluation.

What should I check if automated pull request review fixes are not working?

If automated PR review fixes are not working, verify that your local branch exactly matches the PR head, the git repository is properly configured, and the GitHub CLI is authenticated to allow safe fetching of comments and pushing of commits.