pr-manager

Generate pull request summaries from commits and manage PR creation and merging via GitHub CLI.

25|5|Updated Jun 15, 2024
One-click install
npx skills add https://github.com/OreStudio/OreStudio --skill pr-manager-orestudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-manager
Source: https://github.com/OreStudio/OreStudio/tree/main/.claude/skills/pr-manager
Command: npx skills add https://github.com/OreStudio/OreStudio --skill pr-manager-orestudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the PR workflow by automatically generating a clear summary from commits and guiding the creation, review, and merging of pull requests.

Core Features & Use Cases

  • PR Summary Generation: Build a concise PR title and overview from commit messages and a branch point.
  • PR Lifecycle Management: Create the PR, guide through reviews, and merge once CI passes.
  • Use Case: When delivering a feature across multiple commits, generate the PR body and automate the handoff to reviewers.

Quick Start

  1. Ensure your local branch contains the commits you want to include in the PR.
  2. Run the skill from the repository root.
  3. The skill will generate a PR title and overview, create the PR, and guide you through the review and merge process.

Frequently Asked Questions about pr-manager

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

FAQPage Schema
How do I generate a pull request summary from git commits automatically?

Generate a pull request summary by using standard Git commands like merge-base and git log to extract commit messages from your feature branch. The skill compiles these commits into a concise PR title and overview, forming the body for your GitHub pull request.

How do I automate the GitHub PR lifecycle from creation to merge?

Automate the GitHub PR lifecycle by using the GitHub CLI to compose the PR body, create the pull request, and manage the merge process. The skill guides you through review and merges the branch once CI passes.

Do I need the GitHub CLI installed to automate PR creation?

Yes, you need the GitHub CLI installed because the skill uses it to compose the PR body, create the PR, and manage the merge process. Standard Git commands are also used to gather commit logs and find the branch point.

What is the best way to manage a multi-commit feature branch before merging?

Manage a multi-commit feature branch by automatically generating a clear PR summary from your commit history. This automates the handoff to reviewers by providing a concise title and overview before merging after CI passes.

Can I use this to guide PR reviews and merges after CI passes?

Yes, you can guide PR reviews and merges after CI passes. The skill manages the entire pull request lifecycle, stepping through the review process and handling the final merge once continuous integration checks are complete.

Why does my PR summary not include all commits from the feature branch?

PR summaries might miss commits if the branch point is incorrectly identified. The skill uses standard Git commands like merge-base and git log to find the branch point and extract all subsequent commit messages for the overview.