skills.rest
lklimek
lklimekCOMMUNITY
Explore all skills by this author →
GitHub

check-pr-comments

Verify GitHub Pull Request review comments against current code.

1|Updated Feb 20, 2026
Search Tags:#code quality#code review#pull request#developer workflow#github#comment verification
One-click install
npx skills add https://github.com/lklimek/claudius --skill check-pr-comments
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-pr-comments
Source: https://github.com/lklimek/claudius/tree/main/skills/check-pr-comments
Command: npx skills add https://github.com/lklimek/claudius --skill check-pr-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all review comments on a Pull Request have been properly addressed in the code, preventing regressions and maintaining code quality.

Core Features & Use Cases

  • Automated Comment Verification: Checks if code changes align with the intent of review comments.
  • Status Reporting: Provides a summary of resolved vs. unresolved comments.
  • Structured Reporting: Optionally generates a report.json for further processing or interactive triage.
  • Thread Resolution: Facilitates the resolution of addressed review threads on GitHub.

Quick Start

Use the check-pr-comments skill to verify that all comments on pull request number 123 have been addressed.

Frequently Asked Questions about check-pr-comments

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

FAQPage Schema
How do I verify that GitHub pull request comments have been addressed in the code?▼

Verifying GitHub pull request comments are addressed involves fetching review comments, checking out the PR branch, and semantically comparing each comment against current code changes. This automated comment verification prevents regressions and maintains code quality.

Can I automatically resolve addressed review threads on GitHub pull requests?▼

Yes, you can automatically resolve addressed review threads on GitHub. After semantically verifying that code changes align with the comment intent, the skill facilitates thread resolution on GitHub upon user confirmation.

How does semantic comment verification work for code reviews?▼

Semantic comment verification works by fetching pull request comments, checking out the branch, and analyzing the code to determine if changes align with the intent of each review comment. It then reports resolved versus unresolved items.

Can I generate a structured report of unresolved pull request comments?▼

Yes, you can generate a structured report of unresolved pull request comments. The verification process optionally produces a report in JSON format for further processing, interactive triage, and tracking of resolved versus unresolved code review items.

Do I need GitHub API credentials to check if PR comments are resolved?▼

You need GitHub API access to check if PR comments are resolved. The skill relies on GitHub MCP tools or fallback CLI scripts for API interaction, requiring appropriate authentication to fetch comments and resolve threads.

What's the best way to track unresolved code review comments across a developer workflow?▼

The best way to track unresolved code review comments is to automate verification by fetching PR comments, checking out the branch, and semantically comparing them against code changes to generate a status report of resolved versus unresolved items.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

collect-pr-feedback

Collect and consolidate GitHub pull request feedback and CI check statuses.

Official
Intermediate
JesusFilmJesusFilm
25

handle-pr-review

Automate triage and resolution of GitHub PR review comments via GraphQL.

Official
Advanced
nicolanoviellnicolanoviell
2

code-review

Review code changes for bugs, style issues, and best practices.

Community
Intermediate
ma08ma08
28

gh-address-comments

Fetches and triages GitHub PR comments via CLI.

Community
Intermediate