skills.rest
Andreicr1
Andreicr1COMMUNITY
Explore all skills by this author →
GitHub

previous-comments-reviewer

Compare prior PR review comments against the current diff to identify unaddressed feedback.

Updated Mar 14, 2026
Search Tags:#review#comments#diff#code-review#pull-request#prior-feedback
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill previous-comments-reviewer-andreicr1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: previous-comments-reviewer
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/previous-comments-reviewer
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill previous-comments-reviewer-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps PR reviewers verify that prior feedback has been addressed in the current diff, preventing overlooked changes and regression of previously requested fixes.

Core Features & Use Cases

  • Prior-comment tracking: Detect unaddressed or partially addressed feedback from previous reviews.
  • Diff comparison: Compare current changes against prior comments to confirm resolution.
  • Use Case: When a PR contains existing review threads, surface remaining actionable items that must be resolved before merging.

Quick Start

Identify unaddressed or partially addressed review comments in the current PR diff and report findings.

Frequently Asked Questions about previous-comments-reviewer

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

FAQPage Schema
How do I check if prior code review comments were addressed in a pull request?▼

To check if prior code review comments were addressed, fetch PR metadata and review data, then compare the current diff against existing review threads to identify unaddressed, partially addressed, or regressed feedback.

What is the best way to track unaddressed feedback across multiple PR reviews?▼

Tracking unaddressed feedback across PR reviews involves analyzing existing review threads and comparing them to the current diff to surface remaining actionable items that must be resolved before merging.

How does PR comment regression detection work with existing review threads?▼

PR comment regression detection works by comparing current code changes against prior comments to verify resolution, reporting whether previous review feedback remains unaddressed, partially addressed, or regressed.

Can I verify partially addressed code review feedback in a current diff?▼

Yes, you can verify partially addressed feedback by comparing the current diff to prior comments, which reports the status of existing review threads to confirm whether requested fixes have been fully resolved.

Why do I need to review prior comments before merging a pull request?▼

Reviewing prior comments before merging prevents overlooked changes and regression of previously requested fixes by ensuring that all actionable feedback from existing review threads has been addressed in the current diff.

Does prior feedback tracking work without additional dependencies?▼

Yes, prior feedback tracking works without additional dependencies, as it directly fetches PR metadata and review data to compare changes against prior comments and return a structured findings array.

Related Skills

Explore More Software Engineering Skills→
tech-leads-clubtech-leads-club
5.0k

gh-address-comments

Fetch GitHub pull request comments, reviews, and threads for the current branch.

Official
Intermediate
jitraponjitrapon
11

review-pr

Fetch and summarize GitHub pull request review comments by status.

Community
Intermediate
refernandesrefernandes

swarm-pr-feedback

Automate intake, verification, and resolution of pull request feedback.

Community
Advanced
shonenmshonenm
2

conflict-resolve

Resolve Git merge and rebase conflicts by analyzing base, ours, and theirs states.

Community
Advanced