skills.rest
Epiphytic
EpiphyticOFFICIAL
Explore all skills by this author →
WebsiteGitHub

open-pr

Create structured pull request descriptions from git branch changes and diffs.

7|Updated Feb 6, 2026
Search Tags:#git#code review#pull request#developer workflow#github#pr description
One-click install
npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill open-pr-epiphytic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/Epiphytic/ai-plugin-translator/tree/main/packages/core/test/fixtures/regression-output/workmux/skills/open-pr
Command: npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill open-pr-epiphytic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers turn repository changes and conversation context into structured pull request descriptions, reducing the effort needed to summarize work and prepare reviews.

Core Features & Use Cases

  • PR Context Gathering: Collects branch information, diffs, commit messages, and changed file context before drafting a pull request.
  • Description Generation: Creates concise PR titles and organized summaries covering changes, rationale, and testing details.
  • Use Case: A developer finishing a feature can use this Skill to prepare a consistent pull request description and open the browser-based PR creation flow.

Quick Start

Use the open-pr skill to review my current branch changes and prepare a pull request description.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I generate a pull request description from git branch changes?▼

To generate a pull request description from git branch changes, the Skill collects branch information, diffs, and commit messages to draft a structured PR summary covering changes, rationale, and testing details.

What is the best way to summarize code review context for a new GitHub PR?▼

The best way to summarize code review context for a GitHub PR is to extract repository state information and format concise summaries that outline the development rationale and testing details.

Can I prepare a structured PR title and summary directly from my development workflow?▼

Yes, you can prepare a structured PR title and summary directly from your developer workflow by analyzing repository changes and formatting concise pull request descriptions with browser-based creation support.

Do I need to manually collect git diffs and commit messages before drafting a PR description?▼

You do not need to manually collect git diffs and commit messages before drafting a PR description, as the Skill automatically gathers repository state information and changed file context.

Does this approach work with standard git branches and browser-based PR creation flows?▼

Yes, this approach works with standard git branches and browser-based PR creation flows by applying software engineering workflows involving git diffs and code review preparation.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
arakitakashiarakitakashi
1

create-pr

Create GitHub pull requests with titles and bodies from code diffs.

Community
Intermediate
zli5460zli5460
2

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merging.

Community
Intermediate
VitaDynamicsVitaDynamics

pr-summary-cn

Generate concise Chinese summaries from Git pull request commit history and code differences.

Official
Basic