process-pr

Processes GitHub PRs by evaluating comment-based review status and executing CLI actions.

125|16|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/aaddrick/claude-pipeline --skill process-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-pr
Source: https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/process-pr
Command: npx skills add https://github.com/aaddrick/claude-pipeline --skill process-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines PR handling by interpreting code-review outcomes and performing downstream actions such as merging, closing issues, and creating follow-up work items.

Core Features & Use Cases

  • Automated PR handling: Validate PR and associated issue status, fetch PR data, parse review status from comments, and execute the appropriate path (merge and close or re-run implementation).
  • Follow-up issue orchestration: Create and attach new issues based on review feedback and comments.
  • Rework loop: When changes are requested, trigger a re-implementation flow and re-check the PR until it lands.

Quick Start

Use the process-pr skill to process a PR by providing the PR number, the associated issue number, and the base branch to re-implement if needed. Example: /process-pr 142 130 aw-next

Frequently Asked Questions about process-pr

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

FAQPage Schema
How do I automate GitHub pull request processing after code review?

Automate pull request processing by interpreting code-review outcomes from PR comments and triggering downstream actions. The workflow parses review status to automatically execute merges, close linked issues, or trigger re-implementation loops when changes are requested.

How does automated PR handling manage follow-up issues from review feedback?

Automated PR handling manages follow-up issues by parsing code-review feedback and creating new GitHub issues. It attaches these follow-up work items directly to the original PR based on reviewer comments, ensuring requested changes are tracked and orchestrated.

What is the best way to trigger a rework loop for a GitHub PR requiring changes?

Trigger a rework loop by providing the PR number, associated issue number, and base branch. When the PR review status indicates CHANGES_REQUESTED, the automation initiates a re-implementation flow and continuously re-checks the PR until it successfully lands.

Can I use CLI to merge pull requests and close issues based on GitHub review status?

Yes, you can use CLI to merge pull requests and close issues based on GitHub review status. The automation validates the PR and associated issue status, fetches PR data, parses APPROVED comments, and executes the merge and issue closure via CLI commands.

What information do I need to provide to process a pull request using automation?

To process a pull request, you need to provide the PR number, the associated GitHub issue number, and the base branch name. These inputs allow the automation to validate status, parse reviews, and trigger re-implementation if changes are requested.

When should I not use automated PR processing for GitHub workflows?

You should not use automated PR processing for GitHub workflows requiring manual intervention or complex manual approvals outside of standard APPROVED or CHANGES_REQUESTED statuses. The automation relies on parsing specific review statuses from comments to trigger downstream actions.