review-pending-pr-reviews

Reviews, grills, and posts pending GitHub PR review drafts from a local triage outbox.

29.3k|3.0k|Updated Aug 11, 2017
One-click install
npx skills add https://github.com/nrwl/nx --skill review-pending-pr-reviews
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pending-pr-reviews
Source: https://github.com/nrwl/nx/tree/main/.claude/skills/review-pending-pr-reviews
Command: npx skills add https://github.com/nrwl/nx --skill review-pending-pr-reviews

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated PR review pipelines produce draft reviews that should never reach GitHub without human approval. This Skill provides the human gate: it lists pending review drafts, checks them for drift against the live PR, grills each finding with the maintainer, and only then posts, closes, or discards.

Core Features & Use Cases

  • Pending draft triage: Scans the triage directory for drafts with an empty posted_at field and presents them oldest-first with verdict, attempt, and summary.
  • Drift and staleness detection: Compares stored head_sha against the current PR head via gh pr view, flagging stale, closed, draft, or old-pipeline drafts before any action.
  • Interactive finding grill: Walks the maintainer through Critical and Important findings in rounds, dropping or re-tiering findings and recomputing the verdict before posting.
  • Controlled posting and closing: Posts reviews via gh pr review with verdict-mapped flags, or closes superseded/unnecessary PRs with tailored comments, recording everything in the draft file.
  • Use Case: A cron job ran /review-pr overnight across a dozen PRs. In the morning, invoke this Skill to walk through each pending draft, verify the findings still hold, and post the approved reviews to GitHub.

Quick Start

Ask the assistant to go through the pending PR review outbox and post the approved reviews to GitHub.

Frequently Asked Questions about review-pending-pr-reviews

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

FAQPage Schema
How do I post pending PR review drafts to GitHub?

List drafts in the triage directory where `posted_at` is empty, verify each against the live PR with `gh pr view`, grill the findings, then post with `gh pr review` using the flag matching the verdict. The draft file is updated with `posted_at` and the posted URL.

How do I check if a saved PR review draft is stale?

Compare the draft's `head_sha` frontmatter field against the current PR head from `gh pr view --json headRefOid`. If they differ, the draft is stale and should be skipped in favor of a fresh review run.

Can I close a superseded PR without posting a review?

Yes. For drafts with verdict `superseded`, use the close-with-pointer flow: post a short comment naming the superseding PR via `gh pr comment`, then close with `gh pr close`. No formal review is posted.

What happens to draft files after a review is posted?

The file is never deleted. Its `posted_at` field is set, the posted URL is recorded, and an entry is appended to the `## Posted` section so it feeds re-review deduplication in future runs.

Why should automated PR reviews not be posted without human review?

Headless review runs skip interactive verification, so findings may be wrong, pre-existing, or mis-tiered. Posting them unreviewed publishes unverified claims on public PRs, which is why a human grill gate is required before posting.