skills.rest
ybbms777
ybbms777COMMUNITY
Explore all skills by this author →
GitHub

previous-comments-reviewer

Verify prior GitHub pull request review feedback against the current code diff.

1|Updated Apr 4, 2026
Search Tags:#code quality#code review#github#pr review#review feedback#comment tracking
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill previous-comments-reviewer-ybbms777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: previous-comments-reviewer
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/agent-previous-comments-reviewer
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill previous-comments-reviewer-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When reviewing pull requests, it is easy to miss whether feedback from earlier review cycles was properly addressed, leading to dropped issues, partial fixes, or regressions that slip through to merge.

Core Features & Use Cases

  • Institutional review memory: Acts as a dedicated reviewer that tracks all prior review comments and threads on a PR, cross-referencing them against the current code diff to catch gaps other reviewers miss.
  • Smart false positive filtering: Automatically excludes resolved threads, stale comments on deleted code, author self-notes, and optional nit-level suggestions to eliminate noise.
  • Use case: Use this during final PR review before merge to verify that all requested changes from previous review rounds have been fully implemented, and no previously fixed issues have been accidentally reverted.

Quick Start

Use the previous-comments-reviewer skill to check if all prior review feedback on your current open pull request has been properly addressed in the latest code changes.

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 previous PR review comments were addressed in a new code diff?▼

To check if previous PR review comments were addressed, you need a tool that cross-references historical GitHub pull request threads against the current code diff to identify unaddressed feedback, partial fixes, and regressions automatically.

What is the best way to track unaddressed GitHub pull request review feedback?▼

Tracking unaddressed GitHub pull request review feedback requires fetching PR metadata and historical review threads via the GitHub CLI, then filtering out resolved comments, stale notes on deleted code, and optional nit-level suggestions to return only actionable findings.

Can I automatically catch regressions of previously resolved issues during code review?▼

Yes, you can automatically catch regressions of previously resolved issues during code review by comparing prior review threads against the current pull request diff to verify that previously fixed problems have not been accidentally reverted.

Do I need the GitHub CLI to review prior pull request comments?▼

Yes, you need the GitHub CLI installed and access to PR metadata, because the tool fetches historical review data and existing review threads directly from GitHub to cross-reference them against your current code changes.

How does comment tracking filter out resolved threads and stale review feedback?▼

Comment tracking filters out resolved threads and stale review feedback by automatically excluding resolved conversations, comments on deleted code, author self-notes, and optional nit-level suggestions to eliminate noise and return high-confidence actionable findings.

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
OmniNode-aiOmniNode-ai
3

fix-prs

Automate GitHub Pull Request repairs across organization repositories.

Official
Advanced
FrekiManagarmFrekiManagarm

github-code-review

Coordinate multi-agent GitHub pull request reviews across security, performance, style, and architecture.

Community
Advanced
io-wyio-wy

code-reviewer

Analyze code diffs and files for bugs, vulnerabilities, and code smells.

Community
Advanced