skills.rest
nieomylnieja
nieomylniejaCOMMUNITY
Explore all skills by this author →
GitHub

github-post-pr-review

Posts pending GitHub PR reviews from the latest local review file via gh CLI.

3|Updated Jul 13, 2020
Search Tags:#automation#workflow#api#github#review#pr#dedup
One-click install
npx skills add https://github.com/nieomylnieja/dotfiles --skill github-post-pr-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-post-pr-review
Source: https://github.com/nieomylnieja/dotfiles/tree/main/config/agents/skills/github-post-pr-review
Command: npx skills add https://github.com/nieomylnieja/dotfiles --skill github-post-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, tr, and includes scripts (resource) components.

What problem does it solve?

Post PR review findings as a GitHub pending review via the API. Use after completing a PR review when the user wants to publish findings to GitHub. Reads the most recent review from $XDG_DATA_HOME/agents/pr-review/.

Core Features & Use Cases

  • Load the most recent local PR review for the current branch.
  • Fetch PR metadata and the status of an existing pending review, deduplicating inline findings against existing comments.
  • Post findings to an existing pending review or create a new pending review, formatting inline findings as bold severity tags.
  • Supports a complete end-to-end workflow from local review file to GitHub PR review via gh commands.

Quick Start

Run the post-pr-review workflow on the current branch to publish the latest local review findings to GitHub.

Frequently Asked Questions about github-post-pr-review

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

FAQPage Schema
How do I publish local PR review findings to GitHub as a pending review?▼

Publishing local PR review findings to GitHub involves reading the latest review file from the XDG data store and using gh CLI commands to create or update a pending review on the corresponding PR, deduplicating inline findings against existing comments.

How does deduplication work when posting inline PR findings via the GitHub API?▼

Deduplication of inline PR findings works by fetching existing PR metadata and pending review status, then comparing new findings against existing comments to prevent duplicate postings on the GitHub PR.

Do I need the gh CLI to post GitHub PR reviews from local files?▼

Yes, you need the gh CLI to post GitHub PR reviews from local files, as the workflow relies on gh commands to fetch PR metadata and interact with the GitHub API for creating or updating pending reviews.

What format are inline findings posted in when creating a GitHub pending review?▼

Inline findings are posted as bold severity tags when creating a GitHub pending review. The workflow formats the local review data into this structure before publishing it via the GitHub API.

Can I update an existing pending review instead of creating a new one on GitHub?▼

Yes, you can update an existing pending review. The workflow fetches the status of any existing pending review and appends new findings to it, or creates a new pending review if one does not exist.

Where does the workflow read local PR review files from before posting to GitHub?▼

The workflow reads local PR review files from the $XDG_DATA_HOME/agents/pr-review/ directory, identifying the most recent review file for the current branch to publish to GitHub.

Related Skills

Explore More Software Engineering Skills→
shawnriceshawnrice
3

review

Fetch and analyze GitHub PR details for educational code review.

Community
Advanced
webrix-aiwebrix-ai
1

pr-automation

Automate GitHub pull request workflows for reviewer assignment, labeling, and merge policy enforcement.

Official
Advanced
narusenianarusenia

pr-comment

Post PR review findings as GitHub inline comments.

Community
Advanced
takuto277takuto277

github-pr-review

Post inline review comments on GitHub Pull Requests using the gh CLI.

Community
Advanced