manage-pr

Create pull requests via GitHub CLI and monitor CI checks until merge readiness.

3|1|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/JacobPEvans/claude-code-plugins --skill manage-pr-jacobpevans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-pr
Source: https://github.com/JacobPEvans/claude-code-plugins/tree/main/github-workflows/skills/manage-pr
Command: npx skills add https://github.com/JacobPEvans/claude-code-plugins --skill manage-pr-jacobpevans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating, monitoring, and preparing pull requests for merging, ensuring code quality and efficient review cycles.

Core Features & Use Cases

  • Automated PR Creation: Kicks off the PR process immediately after work is complete.
  • CI/CD Monitoring: Watches for checks to pass and ensures all conversations are resolved.
  • Pre-Merge Validation: Verifies that all checks are passing and the PR is mergeable before user intervention.
  • Use Case: After completing a feature, use this Skill to automatically create a PR, monitor its CI status, and notify you when it's ready for a final review and merge.

Quick Start

Use the manage-pr skill to create and manage the current pull request.

Frequently Asked Questions about manage-pr

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

FAQPage Schema
How do I automate pull request creation and CI check monitoring in GitHub?

You can automate the pull request lifecycle by pushing code and creating PRs via GitHub CLI, then monitoring CI/CD checks and resolving review threads before signaling merge readiness.

What is the best way to manage a pull request from creation to merge readiness?

Managing a pull request from creation to merge readiness requires automating code pushes, creating the PR via GitHub CLI, monitoring CI checks, and resolving all conversations to verify mergeability before user intervention.

Does this PR automation work with GitHub CLI and existing CI/CD pipelines?

Yes, this PR automation works with GitHub CLI and existing CI/CD pipelines by monitoring checks to pass and ensuring review threads are resolved before signaling readiness for user-initiated merge.

How do I ensure all CI checks pass and review conversations are resolved before merging a PR?

To ensure CI checks pass and review conversations are resolved before merging, the automation monitors CI/CD status and verifies all threads are resolved, only signaling merge readiness after pre-merge validation succeeds.

Can I automatically verify PR mergeability without manual checks?

You can automatically verify PR mergeability by monitoring CI/CD checks and resolving conversations programmatically, ensuring the PR is fully mergeable before requesting user intervention for the final merge.

When should I use automated pull request monitoring instead of manual reviews?

Automated pull request monitoring is ideal after completing a feature, allowing you to automatically create a PR, monitor its CI status, and receive notifications when it is ready for final review and merge.