update-pr-review

Name: update-pr-review
Availability: InStock
Author: Warp

Aggregate pull request review threads to update local SKILL.md files.

292|39|Updated Mar 17, 2026

Search Tags:#automation #feedback #github #review #pull-request #companion #local-skill

Ready to run

npx skills add https://github.com/warpdotdev/oz-for-oss --skill update-pr-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-pr-review
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/update-pr-review
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill update-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Aggregates real reviewer feedback to refine the repo-local PR review companions (review-pr-local and review-spec-local), strengthening consistency with the core contracts.

Core Features & Use Cases

Routes feedback from code and spec PR review conversations to the appropriate local SKILLs without altering core contracts.
Supports an auditable improvement loop by constraining edits to local SKILLs only and tracking changes.
Enables targeted updates based on repeated reviewer signals to reduce misinterpretation of feedback.

Quick Start

Update the local review-pr-local and review-spec-local SKILL.md files with the latest reviewer feedback.

Frequently Asked Questions about update-pr-review

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

FAQPage Schema

How do I use GitHub pull request review comments to improve automated PR review rules?▼

You can aggregate GitHub pull request review comments to refine automated PR review rules by routing threaded reviewer feedback directly into repository-local SKILL.md configuration files, creating an auditable improvement loop for your review companions.

Can I update local PR review skills without altering the core automation contracts?▼

Yes, you can update local PR review skills without altering core contracts because the process constrains all edits exclusively to local SKILL.md files under the .agents/skills directory, leaving core SKILLs completely untouched and maintaining system stability.

How does aggregating reviewer feedback on pull requests work for code and spec reviews?▼

Aggregating reviewer feedback on pull requests works by reading review threads and issue comments, partitioning the feedback by review type, and applying those targeted updates to both code and spec review companion skills for consistent local refinement.

What is the best way to apply repeated reviewer signals to reduce misinterpreted PR review feedback?▼

The best way to apply repeated reviewer signals to reduce misinterpreted PR review feedback is to partition threaded comments by review type and use them to perform targeted updates on local review skills, ensuring consistent application of reviewer expectations.

Does this local PR review feedback update process require modifying core repository skills?▼

No, the local PR review feedback update process does not require modifying core repository skills, as it strictly isolates changes to the local review-pr-local and review-spec-local SKILL.md files to ensure an auditable and safe improvement loop.

Why should I partition GitHub PR review feedback by review type when updating local skills?▼

You should partition GitHub PR review feedback by review type when updating local skills because it enables targeted updates to the correct local SKILL.md files, preventing misinterpretation and ensuring feedback is accurately routed to code or spec review flows.