skills.rest
narusenia
naruseniaCOMMUNITY
Explore all skills by this author →
Website𝕏@mino_anythingGitHub

pr-comment

Post PR review findings as GitHub inline comments.

Updated Apr 13, 2026
Search Tags:#github#code-review#pull-request#inline-comments#review-automation#diff-validation
One-click install
npx skills add https://github.com/narusenia/skills --skill pr-comment-narusenia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-comment
Source: https://github.com/narusenia/skills/tree/main/pr-comment
Command: npx skills add https://github.com/narusenia/skills --skill pr-comment-narusenia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns PR review findings into GitHub inline comments, so reviewers can move from analysis to actionable feedback without manually placing each note.

Core Features & Use Cases

  • Posts review notes as inline comments on the correct pull request files and lines.
  • Validates comment locations against the diff and redirects out-of-range notes to the review body when needed.
  • Supports comment files or context-based generation, plus review event selection such as comment, request changes, or approve.
  • Use it when you have a structured PR review and want to publish it quickly with consistent formatting.

Quick Start

Ask this skill to post the review notes for a pull request as GitHub inline comments, providing the PR number or URL and an optional markdown file with your comments.

Frequently Asked Questions about pr-comment

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

FAQPage Schema
How do I post code review findings as GitHub inline comments on a pull request?▼

To post code review findings as GitHub inline comments, provide your structured notes, the PR number or URL, and commit metadata to automate comment placement on the correct diff lines.

What happens to inline PR comments when review notes fall outside the diff range?▼

When review notes fall outside the validated diff range, they are automatically redirected from inline comments to the main pull request review body to ensure submission succeeds.

Can I select a specific GitHub review event when submitting automated PR comments?▼

Yes, you can select a specific GitHub review event when submitting PR comments, choosing to submit as a standard comment, request changes, or approve the pull request.

Do I need GitHub PR metadata to automate pull request review submission?▼

Yes, GitHub PR metadata and commit identity are required to validate diff ranges, format comments to match API constraints, and successfully submit your automated pull request review.

What is the best way to format structured review notes for GitHub pull request APIs?▼

The best way to format structured review notes for GitHub APIs is using a markdown file or context-based generation that matches GitHub review API constraints for proper inline comment rendering.

Why are my automated PR inline comments failing to attach to the correct file lines?▼

Automated PR inline comments fail when comment locations are not validated against the PR diff, requiring diff-range validation and file redirection to correctly map notes to file lines.

Related Skills

Explore More Software Engineering Skills→
adryanevadryanev
2

review-pr

Post inline code review comments on GitHub pull requests using the gh CLI.

Community
Advanced
rickyanandarickyananda
1

github-code-review

Reviews GitHub pull requests and local diffs for security and quality issues.

Community
Advanced
Dawn-TechnologyDawn-Technology
9

review-pr

Generate evidence-based review findings for GitHub Pull Requests or GitLab Merge Requests.

Official
Advanced
mmartinsolivmmartinsoliv

pr-review-pending

Create pending GitHub pull request review comments from code review findings.

Community
Advanced