verify-review

Parse PR review feedback and validate subsequent commits against checklist items.

50|17|Updated Sep 2, 2023
One-click install
npx skills add https://github.com/bkelly-lab/jkp-data --skill verify-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-review
Source: https://github.com/bkelly-lab/jkp-data/tree/main/.claude/skills/verify-review
Command: npx skills add https://github.com/bkelly-lab/jkp-data --skill verify-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that PR authors address prior review feedback by locating the PR, extracting the reviewer’s structured feedback, and checking subsequent commits against the checklist.

Core Features & Use Cases

  • Checklist parsing: automatically identify structured feedback items from the reviewer’s comments.
  • Diff-based verification: compare new commits against the review items to confirm each item is addressed.
  • Guided re-review: produces a concise summary of which items are addressed, partially addressed, or missing, and suggests next steps for the reviewer.

Quick Start

Run this skill on a pull request to automatically verify that the reviewer’s checklist has been addressed in the latest commits.

Frequently Asked Questions about verify-review

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

FAQPage Schema
How do I verify that a pull request addresses prior code review feedback?

You can verify PR review feedback by parsing reviewer comments, identifying subsequent commits, and comparing diffs against the checklist to generate a structured verdict on whether each item is addressed, partially addressed, or missing.

What is the best way to automate checking if PR review checklist items are resolved?

The best way to automate PR review checklist verification is to extract structured feedback from GitHub comments, fetch subsequent commits and diffs, and automatically evaluate whether each checklist item is fully addressed in the updated code.

How does diff-based verification work for updated pull request commits?

Diff-based verification works by fetching new pull request commits, analyzing the code changes, and matching those diffs against the structured reviewer checklist to determine if requested modifications have been implemented in the updated code.

Can I use this to check GitHub pull request comments against new commits?

Yes, this supports typical GitHub-based collaboration workflows by extracting reviewer comments, identifying subsequent response commits, and fetching diffs to validate that all review items are satisfied in the updated pull request.

Do I need access to the Git repository to verify PR review feedback?

Yes, you need access to the Git repository, the specific pull request, and the ability to fetch comments, commits, and diffs to determine whether all reviewer checklist items have been successfully addressed by the author.