pr-github-ops

Post Superagent PR security scan findings as inline GitHub review comments via gh CLI.

76|11|Updated May 18, 2026
One-click install
npx skills add https://github.com/superagent-ai/skills --skill pr-github-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-github-ops
Source: https://github.com/superagent-ai/skills/tree/main/skills/pr-github-ops
Command: npx skills add https://github.com/superagent-ai/skills --skill pr-github-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post Superagent PR security scan findings as inline GitHub review comments using the gh CLI. You own GitHub side effects after handoff: inline finding comments, managed labels, and check-run completion.

Core Features & Use Cases

  • Inline review comments anchored to diff lines for actionable findings.
  • Manage PR labels and complete the PR check run in a single workflow.
  • Use during sandbox PR handoffs to surface security findings on GitHub without thread comments.

Quick Start

Run a PR security scan and post findings inline to the PR using gh.

Frequently Asked Questions about pr-github-ops

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

FAQPage Schema
How do I post security scan findings as inline GitHub PR review comments?

To post security scan findings as inline GitHub PR review comments, this Skill uses the gh CLI to anchor findings directly to PR diff lines. It reads scan context and submits inline reviews to surface actionable results on GitHub.

Can I manage PR labels and check runs automatically after a security scan?

You can manage PR labels and check runs automatically after a security scan. The Skill updates PR labels and completes check runs in a single workflow alongside posting inline review comments.

Do I need gh CLI authentication to post inline PR review comments?

Yes, you need gh CLI authentication to post inline PR review comments. The Skill requires gh CLI access and a pr-scan-context.json file containing the PR context to anchor and submit findings.

What is the best way to surface security findings on GitHub without thread comments?

The best way to surface security findings without thread comments is posting inline review comments anchored to diff lines. This approach provides actionable feedback directly on the code changes during sandbox PR handoffs.

How does posting inline PR reviews work during sandbox PR handoffs?

During sandbox PR handoffs, posting inline PR reviews works by reading the pr-scan-context.json file and using gh CLI to anchor security findings to specific diff lines. This surfaces issues directly on GitHub PRs.

Why use inline GitHub reviews instead of general PR comments for scan findings?

Inline GitHub reviews anchor scan findings to exact diff lines, providing actionable context that general PR comments lack. This ensures developers see security issues directly in the code changes.