review-code-follow-up

Rechecks prior code review findings against the author's response delta and writes a follow-up report.

716|31|Updated Mar 13, 2023
One-click install
npx skills add https://github.com/wimpysworld/nix-config --skill review-code-follow-up
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code-follow-up
Source: https://github.com/wimpysworld/nix-config/tree/main/home-manager/_mixins/agentic/assistants/skills/review-code-follow-up
Command: npx skills add https://github.com/wimpysworld/nix-config --skill review-code-follow-up

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After an author responds to a code review, reviewers need to verify which findings were actually fixed without rerunning the entire review from scratch. This Skill rechecks each prior finding against the current code and inspects only the changes made in response.

Core Features & Use Cases

  • Finding Verification: Reproduces every actionable finding from the prior report and assigns a status of resolved, partly resolved, unresolved, or withdrawn with concise proof.
  • Response Delta Review: Inspects only the changes between the previously reviewed SHA and the current head for defects caused by the author's response, preserving the original lens and severity bar.
  • Structured Follow-up Report: Writes a code-review-again.md report in a new timestamped run directory, keeping GitHub access read-only and the report private.
  • Use Case: A reviewer asked an author to fix a null-pointer bug and add a test. After the author pushes new commits, run this Skill to confirm the fix works, verify the test exists, and check the new commits did not introduce regressions.

Quick Start

Ask the assistant to re-review the pull request and verify the author's fixes against the previous code review report.

Frequently Asked Questions about review-code-follow-up

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

FAQPage Schema
How do I verify fixes from a previous code review?

Run a follow-up review that reloads the prior report, reproduces each actionable finding against the current code, and assigns a status of resolved, partly resolved, unresolved, or withdrawn with proof. It also inspects only the commits made since the reviewed SHA.

How to re-review a pull request after the author responds?

Provide the pull request target or the prior report path, and the Skill locates the latest final report, recovers the original review contract, and checks the delta from the previously reviewed SHA to the current head. GitHub access stays read-only.

Does a follow-up review rerun the full code review?

No. It preserves the original lens and severity bar, rechecks only prior findings, and reviews changed lines plus directly affected callers or tests. It never restarts the wide fan-out or topic sweep from the initial review.

What happens if no prior review report exists?

The Skill lists the available target directories and stops, instructing you to run an initial review command first. It never substitutes a fresh full review for a follow-up.

Can a follow-up review report new defects outside the author's changes?

Only when evidence shows a serious security, data-loss, outage, or production-correctness risk. Unrelated findings the prior review missed are suppressed unless they meet that bar and pass adversarial verification.