skills.rest
mmartinsoliv
mmartinsolivCOMMUNITY
Explore all skills by this author →
Website𝕏@mmartinsolivGitHub

pr-review-pending

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

Updated May 8, 2026
Search Tags:#code review#pull request#github#graphql#inline comments#pending review
One-click install
npx skills add https://github.com/mmartinsoliv/dotfiles --skill pr-review-pending
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-pending
Source: https://github.com/mmartinsoliv/dotfiles/tree/main/agents/skills/pr-review-pending
Command: npx skills add https://github.com/mmartinsoliv/dotfiles --skill pr-review-pending

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn code review findings into pending GitHub review comments without submitting the review, so you can prepare feedback safely before publishing.

Core Features & Use Cases

  • Analyze a pull request and map findings to line-anchored inline comments.
  • Reuse prior review findings or invoke the pr-reviewer agent when needed.
  • Validate diff positions, handle deleted lines, and preserve a single pending review per user.
  • Use case: prepare a batch of review comments for a pull request, share the pending review URL, and let the user submit it from GitHub when ready.

Quick Start

Use the pr-review-pending skill to prepare pending inline review comments for pull request 84 on the current repository.

Frequently Asked Questions about pr-review-pending

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

FAQPage Schema
How do I draft GitHub pull request review comments without submitting them?▼

To draft GitHub pull request review comments without submitting them, you can create pending inline comments mapped to specific diff lines, preserving a single pending review per user to post feedback safely before publishing.

Can I post inline code review comments to a GitHub PR without submitting the full review?▼

Yes, you can post inline code review comments to a GitHub PR without submitting the full review by creating a pending review state, which allows you to anchor feedback to specific diff lines and share the review URL for later submission.

How do I handle deleted lines when anchoring pending review comments on GitHub?▼

Handling deleted lines when anchoring pending review comments on GitHub requires diff position validation to ensure line-anchored feedback maps correctly to the pull request changes without breaking the GraphQL review API submission.

Does the GitHub CLI GraphQL API support creating a single pending review per user?▼

Yes, the GitHub CLI GraphQL API supports creating a single pending review per user, allowing you to safely batch line-anchored inline comments and maintain reproducible draft feedback before final submission.

What is the best way to prepare a batch of code review findings for a GitHub pull request?▼

The best way to prepare a batch of code review findings for a GitHub pull request is to map the findings to line-anchored inline comments within a pending review, enabling safe draft preparation and reproducible comment posting without submitting.

Why does GitHub only allow one pending review per user on a pull request?▼

GitHub only allows one pending review per user on a pull request to maintain a single draft state, so adding new line-anchored comments requires handling the existing pending review safely to avoid duplicate or lost feedback.

Related Skills

Explore More Software Engineering Skills→
gittowergittower
413

pr-review

Create a structured GitHub pull request review draft with inline comments.

Official
Advanced
hyperlane-xyzhyperlane-xyz
97

inline-pr-comments

Post line-specific inline comments to GitHub pull request diffs.

Official
Intermediate
stephendolanstephendolan
2

pull-request

Draft concise GitHub pull request descriptions with summary and problem sections.

Community
Basic
liujiayi3703liujiayi3703

babysit

Monitor pull request status and manage review threads via GitHub CLI.

Community
Intermediate