skills.rest
Pear-Commerce
Pear-CommerceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pear-pr-review-flow

Automate Pear pull request lifecycle from creation to landing.

Updated May 15, 2026
Search Tags:#github#code-review#copilot#git-workflow#pull-request#pr-automation#pear-engineering
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill pear-pr-review-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pear-pr-review-flow
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/pear-pr-review-flow
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill pear-pr-review-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manually managing Pear engineering pull requests is error-prone and often violates team workflow rules, leading to missed reviewer requests, incorrect Copilot assignments, unhandled review feedback, and non-compliant PR merges. This skill eliminates that manual overhead by enforcing Pear's standardized PR workflow end-to-end.

Core Features & Use Cases

  • Compliant PR Creation and Readying: Automatically runs the required Pear engineering cleanup pass before opening or marking a PR ready for review, and defaults new Codex-authored PRs to ready-for-review unless a draft is explicitly requested.
  • Automated Reviewer and Copilot Assignment: Identifies the correct individual engineering reviewers for the repository, requests GitHub Copilot review, and removes accidental broad team reviewer requests to keep review queues targeted.
  • Review Feedback and Watch Automation: Handles incoming review comments, creates configurable recurring watch loops to monitor PR status, auto-fix actionable feedback when approved, and land PRs once they are green, approved, and mergeable, with quiet overnight windows to avoid unnecessary notifications.
  • Use Case: A Pear engineer opening a feature PR to api.pearcommerce.com can use this skill to automatically request the right reviewers, add Copilot, set up a daily watch loop to handle incoming feedback, and merge the PR once all checks pass without manually tracking each step.

Quick Start

Use the pear-pr-review-flow skill to manage the full lifecycle of your Pear engineering pull request from creation to landing, including adding reviewers, requesting Copilot, handling review feedback, and merging the PR once it meets all approval and check requirements.

Frequently Asked Questions about pear-pr-review-flow

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

FAQPage Schema
How do I automate pull request reviews and assignments for my GitHub repositories?▼

Automating pull request reviews involves using scripts to enforce team workflows, automatically assign individual reviewers, request Copilot reviews, and remove broad team reviewer requests to keep queues targeted. This eliminates manual errors and missed assignments.

How does PR automation handle incoming review feedback and merge PRs?▼

PR automation handles review feedback by creating recurring watch loops to monitor status, auto-fixing actionable feedback when approved, and landing pull requests once they are green, approved, and mergeable, with quiet overnight windows to avoid notifications.

Can I use git worktree isolation and CI-first verification for PR workflow automation?▼

Yes, PR workflow automation can enforce isolated git worktree usage and CI-first verification before opening or marking a pull request ready for review, ensuring code passes required cleanup passes and engineering guardrails prior to submission.

What dependencies do I need to run automated git workflow scripts for pull requests?▼

You need gh, git, and python3 installed in your environment to run automated git workflow scripts. These dependencies provide the command-line interfaces and scripting runtime required to execute PR automation and repository interactions.

When should I avoid using automated PR landing loops in continuous integration?▼

You should avoid relying on automated PR landing loops during configured overnight quiet windows, as the automation intentionally pauses monitoring and auto-landing actions to prevent unnecessary notifications and disruptions during off-hours.

Related Skills

Explore More Software Engineering Skills→
MOODMNKY-LLCMOODMNKY-LLC

gh-issues

Convert GitHub issues into merged pull requests using the GitHub CLI.

Community
Advanced
DuySeuDuySeu
1

gsd-ship

Push verified branches, create PRs, trigger reviews, and track merges on GitHub.

Community
Advanced
robinebersrobinebers
46

shepherd

Automate GitHub pull request review management until human approval.

Community
Advanced
HaveAPointHaveAPoint

auto-commit

Automate Git commits, pushes, and pull request creation.

Community
Intermediate