github-pr-comments

Draft and post evidence-based GitHub pull request review comments.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill github-pr-comments-orestesk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-comments
Source: https://github.com/OrestesK/pi/tree/main/skills/github-pr-comments
Command: npx skills add https://github.com/OrestesK/pi --skill github-pr-comments-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns verified code-review findings into clear, actionable GitHub pull request comments while preventing speculative feedback, stale-head reviews, and unsafe mutations.

Core Features & Use Cases

  • Evidence-Based Drafting: Validate findings against source, diffs, checks, documentation, existing comments, and safe live verification.
  • Comment Placement: Choose appropriate inline or general review comments and validate inline anchors against the current diff.
  • Safe Review Posting: Prepare and submit one atomic review payload through the GitHub CLI only after explicit user authorization, with head rechecks and post-submission verification.
  • Use Case: After reviewing a pull request, use this Skill to produce concise comments that include the issue, evidence, verification performed, assumptions, and a specific fix or question.

Quick Start

Ask the GitHub PR comments skill to review your verified findings for a specific pull request and draft or post the appropriate comments.

Frequently Asked Questions about github-pr-comments

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

FAQPage Schema
How do I post inline review comments on a GitHub pull request using the gh cli?

To post inline review comments on a GitHub pull request, this Skill validates diff anchors and submits an atomic review payload through the gh cli. It requires explicit user authorization before performing any mutation to ensure safe comment posting.

What is the best way to draft actionable code review comments for GitHub PRs?

The best way to draft actionable code review comments is to validate findings against source code, diffs, and documentation. This Skill generates concise comments that include the issue, evidence, verification performed, assumptions, and a specific fix or question.

How do I prevent stale-head reviews when submitting GitHub PR comments?

To prevent stale-head reviews when submitting GitHub PR comments, this Skill performs current PR-head verification and live head rechecks before submission. It applies diff-anchor validation to ensure comments attach to the correct code state.

Does this GitHub PR comments tool require explicit authorization before posting reviews?

Yes, this GitHub PR comments tool requires explicit mutation authorization before posting reviews. It prepares and submits one atomic review payload through the GitHub CLI only after receiving user approval to prevent unsafe mutations.

Can I validate inline comment anchors against a current pull request diff before posting?

Yes, you can validate inline comment anchors against a current pull request diff. This Skill checks existing comments and verifies diff anchors to ensure accurate inline placement before submitting the review payload.

What limitations exist when automating GitHub pull request review comments?

Limitations when automating GitHub pull request review comments include the need for explicit mutation authorization and live verification when practical. The Skill avoids speculative feedback by requiring evidence-based findings and current PR-head checks before submission.