pullrequest-review

Verify code review feedback items before implementing changes.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill pullrequest-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pullrequest-review
Source: https://github.com/thermiteau/maverick/tree/main/skills/pullrequest-review
Command: npx skills add https://github.com/thermiteau/maverick --skill pullrequest-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to handle code review feedback, ensuring verification before changes and justified pushback when needed, reducing misinterpretations and rework.

Core Features & Use Cases

  • Verification-driven feedback processing: Read, validate, and respond to each review item against the codebase.
  • Justified pushback: When feedback is ambiguous or incorrect, push back with technical reasoning and requested clarifications.
  • Iterative verification: After each change, re-verify to ensure alignment with project standards and tests.

Quick Start

Provide a review response for a pending PR that reads all feedback items, asks clarifying questions if needed, and outlines concrete next steps for changes.

Frequently Asked Questions about pullrequest-review

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

FAQPage Schema
How do I automate processing code review feedback for pull requests?

Automate code review feedback by reading each item, validating it against the codebase, and responding with structured next steps or justified pushback. This enforces a verification workflow before implementing any changes.

What is the best way to handle incorrect or ambiguous code review comments?

Handle incorrect code review comments by pushing back with technical reasoning and requesting clarifications. The workflow enforces justified rejections to ensure feedback is validated before implementing changes.

How do I verify code changes after addressing pull request review items?

Verify code changes by iteratively re-checking them after each modification. This ensures the fixes align with project standards and tests, confirming the review feedback was fully addressed.

Can I use this to guide interactions with automated code-reviewer agents?

Yes, the workflow applies during interactions with both automated code-reviewer agents and human reviewers, guiding clarifications and structured responses for pending pull requests.

What are the limitations of automated pull request review verification?

Automated verification requires clear technical reasoning for rejection and iterative re-validation after fixes. It does not bypass project standards but enforces them, meaning ambiguous feedback must be clarified before proceeding.