pr-comment

Resolve GitHub PR review comments by parsing URLs and applying verified fixes.

5|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ophidiarium/mehen --skill pr-comment-ophidiarium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-comment
Source: https://github.com/ophidiarium/mehen/tree/main/.agents/skills/pr-comment
Command: npx skills add https://github.com/ophidiarium/mehen --skill pr-comment-ophidiarium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you handle GitHub PR review comments correctly by fetching the exact comment, applying the requested fixes safely, and replying directly to that same comment thread.

Core Features & Use Cases

  • Parse and validate comment links: Extracts owner, repo, PR number, and comment ID from a discussion URL format used by GitHub review comments.
  • Fetch authoritative comment details: Retrieves comment metadata and full body content via the GitHub CLI API call before making any changes.
  • Apply all requested fixes with guardrails: Ensures each suggestion is verified in the current codebase, adds regression coverage when relevant, and fixes any mandatory “nitpick” items without placeholders.
  • Reply with traceability: Posts a direct reply to the specific comment including the short commit SHA and the author’s handle.

Quick Start

Use the pr-comment skill to fix an inline GitHub review comment you are addressing in the current pull request by providing its exact comment link.

Frequently Asked Questions about pr-comment

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

FAQPage Schema
How do I reply to a specific GitHub PR review comment with a fix commit?

To reply to a GitHub PR review comment with a fix, you parse the comment URL, fetch the content via the GitHub API, apply verified code changes, and post a thread-specific reply containing the commit SHA.

What is the correct workflow for resolving inline pull request review comments?

Resolving inline pull request review comments involves fetching the authoritative comment metadata, applying requested code fixes with guardrails, and creating a direct reply to the discussion thread to ensure traceability.

Can I use the GitHub CLI to fetch and reply to pull request comments?

Yes, you can use the GitHub CLI (gh) to retrieve comment details via API calls and create a thread-specific reply after committing the fix directly to the referenced pull request.

Does resolving a GitHub review comment require the exact discussion URL?

Yes, resolving a GitHub review comment requires the exact discussion URL to extract the owner, repo, PR number, and comment ID needed to fetch the correct thread and post a direct reply.

What is the best way to handle nitpicks and code suggestions in a GitHub pull request?

The best way to handle nitpicks and code suggestions is to verify each item in the current codebase, apply fixes without placeholders, add regression coverage if relevant, and reply with the commit SHA.

When should I not use an automated workflow for GitHub PR comment fixes?

You should not use an automated workflow for GitHub PR comment fixes when the review feedback is ambiguous, lacks specific actionable code suggestions, or requires broader architectural discussion outside the inline thread.