pr-comments

Post inline GitHub PR review comments via the gh CLI.

15|7|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/daltoniam/switchboard --skill pr-comments-daltoniam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-comments
Source: https://github.com/daltoniam/switchboard/tree/main/.agents/skills/pr-comments
Command: npx skills add https://github.com/daltoniam/switchboard --skill pr-comments-daltoniam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates posting PR review findings as inline comments on a GitHub PR, eliminating manual copy-paste and ensuring consistent feedback.

Core Features & Use Cases

  • Post inline comments on specific changed lines using the gh CLI and the PR Reviews API.
  • Map findings to the correct diff lines and avoid duplicates by inspecting existing PR comments.
  • Use case: you run a pre-review pass on a PR and automatically publish an inline review with actionable items.

Quick Start

Post inline comments on a PR by mapping findings to the diff with the gh CLI and submitting via the PR Reviews API.

Frequently Asked Questions about pr-comments

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

FAQPage Schema
How do I post inline comments on a GitHub pull request automatically?

You can post inline comments on a GitHub pull request automatically by mapping review findings to specific diff lines and submitting them via the gh CLI and the PR Reviews API.

What is the best way to automate code reviews and leave inline PR comments?

Automating code reviews and leaving inline PR comments is best achieved by running a pre-review pass, mapping findings to the diff, and publishing an inline review via the gh CLI to ensure consistent feedback.

Does posting PR review comments via the gh CLI require special authentication?

Yes, posting PR review comments via the gh CLI requires proper authentication and gh CLI access to submit reviews and prevent duplicate comments by inspecting existing PR comments.

How does the inline PR comment workflow handle duplicate review findings?

The inline PR comment workflow prevents duplicate review findings by inspecting existing PR comments and mapping new findings to the correct diff lines before submitting the review.

Can I map static analysis findings directly to GitHub PR diff lines?

Yes, you can map static analysis findings directly to GitHub PR diff lines by automating the mapping process and posting the results as inline comments using the gh CLI.