skills.rest
nexuslabs-ai
nexuslabs-aiOFFICIAL
Explore all skills by this author →
GitHub

pr-review-follow-up

Re-reviews pull requests to verify prior feedback was addressed and detect new issues.

1|1|Updated Dec 18, 2025
Search Tags:#git#code review#pull request#github#verification#follow-up#review feedback
One-click install
npx skills add https://github.com/nexuslabs-ai/nexus --skill pr-review-follow-up-nexuslabs-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-follow-up
Source: https://github.com/nexuslabs-ai/nexus/tree/main/.agents/skills/pr-review-follow-up
Command: npx skills add https://github.com/nexuslabs-ai/nexus --skill pr-review-follow-up-nexuslabs-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an initial code review, teams need a consistent way to verify that requested changes were actually made and that fixes did not introduce new defects. This Skill automates the follow-up review pass on a pull request, checking each previously raised issue against the new diff. ## Core Features & Use Cases - Issue Verification: Tracks every blocking and minor issue from the previous review and marks it as Fixed, Still Present, Partially Fixed, or Changed. - New Issue Detection: Reviews only the files changed since the last review, flagging regressions or new problems introduced by the fixes. - Dependency Validation: Verifies fixes involving third-party libraries against current documentation via web research. - Use Case: After a developer pushes commits responding to review feedback, run this Skill to produce a structured follow-up review with a verdict (APPROVE, COMMENT, or REQUEST_CHANGES) and inline comments ready to post. ## Quick Start Re-review the current pull request and verify that all issues from the previous review have been addressed.

Frequently Asked Questions about pr-review-follow-up

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

FAQPage Schema
How do I re-review a pull request after changes are pushed?▼

Run a follow-up review that gathers the previous review's issues, identifies commits pushed since then, and verifies each issue against the new diff. The Skill outputs a verdict plus inline comments for the caller to post.

How to verify code review feedback was addressed on GitHub?▼

Compare each prior issue's file and line location against the latest commits. The Skill marks each as Fixed, Still Present, Partially Fixed, or Changed, and only reports unresolved items in the output table.

Does the follow-up review check third-party library fixes?▼

Yes. When a fix changes how a dependency is used or adds a new one, the Skill researches current official documentation via web search to confirm the usage is correct before approving.

What verdicts can a follow-up PR review return?▼

The SDE2 lane returns APPROVED, MINOR CHANGES, or CHANGES REQUIRED based on blocking issue status. The Architect lane returns APPROVED, NEEDS DISCUSSION, or CHANGES REQUIRED for architectural concerns.

When should I not use a follow-up review?▼

Do not use it for a first-pass review of a new pull request; it requires a previous review with documented issues. Use the initial pr-review skill first, then this Skill only after changes are pushed.

Related Skills

Explore More Software Engineering Skills→
saffron-healthsaffron-health
862

get-pr-reviews

Retrieve and format GitHub pull request review comments by file and line.

Official
Intermediate
microsoftmicrosoft
298

review

Automate GitHub pull request reviews with inline comments and verdicts.

Official
Advanced
hardisgroupcomhardisgroupcom
368

test

Build, lint, and test code changes with yarn commands.

Official
Intermediate
theafhtheafh
38

git_commit

Stage the full working tree and generate an evidence-based git commit message.

Community
Advanced