review-staged

Process staged pull request reviews with owner-directed post, skip, draft, or discuss actions.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill review-staged
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-staged
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/review-staged
Command: npx skills add https://github.com/app-vitals/shipwright --skill review-staged

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you walk through already-staged pull request reviews without losing order, context, or owner intent, so review queues can be processed consistently and safely.

Core Features & Use Cases

  • Queue-aware review flow: Handles staged PRs in the correct order, with approvals first and comments afterward.
  • Owner-directed actions: Lets the reviewer choose to post, skip, draft, or discuss each review before anything is sent.
  • Operational safeguards: Skips drafts, WIP branches, stale SHAs, and other risky cases while surfacing CI and Dependabot context.
  • Use case: A team lead wants to drain a backlog of staged reviews across repositories and decide one PR at a time whether to publish feedback.

Quick Start

Use the review-staged skill to walk me through the staged pull request reviews and let me decide whether to post, skip, draft, or discuss each one.

Frequently Asked Questions about review-staged

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

FAQPage Schema
How do I process queued pull request reviews in the correct order?

Processing queued pull request reviews requires handling approvals before comments, sorting by diff size, and presenting one PR at a time. This skill drains staged reviews while maintaining queue order and context for consistent owner-directed actions.

What is the best way to walk through staged PR reviews and decide on each one?

Walking through staged PR reviews is best handled by presenting each review individually for an owner-directed action. You can choose to post, skip, draft, or discuss each pull request before any feedback is sent to GitHub.

Do I need GitHub CLI and task-store records to review staged pull requests?

You need GitHub CLI access, task-store records, staged review markdown and JSON files, and CI status checks to review staged pull requests. These dependencies provide the necessary context and guardrails for safe processing.

How does this workflow handle WIP commits, drafts, and Dependabot pull requests?

Handling WIP commits, drafts, and Dependabot pull requests involves operational safeguards that skip risky cases and surface relevant context. The workflow skips drafts and WIP branches while checking for stale SHAs before processing.

Can I review a backlog of staged pull requests across multiple repositories one at a time?

Reviewing a backlog of staged pull requests across repositories one at a time is supported by this queue-aware flow. A team lead can drain the backlog and decide individually whether to publish feedback, skip, or discuss each item.