skills.rest
hirokimry
hirokimryCOMMUNITY
Explore all skills by this author →
Website𝕏@hirokimryGitHub

pr

Create and update GitHub pull requests from branch diffs and issue context.

1|Updated Mar 20, 2026
Search Tags:#automation#code review#pull request#github#issue linking#pr creation#branch diff
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill pr-hirokimry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/pr
Command: npx skills add https://github.com/hirokimry/vibecorp --skill pr-hirokimry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of preparing GitHub pull requests by turning branch changes, issue context, and repository conventions into a ready-to-review PR with the right title, body, and linkage.

Core Features & Use Cases

  • New PR creation: Builds a PR from the current branch and base branch with a review-friendly summary.
  • PR updates: Edits an existing PR when changes have already been published.
  • Issue linking: Formats issue references correctly so close or reference behavior works as intended.
  • Repository-aware workflow: Reads the repo state, compares diffs, and adapts the PR body to the change type.
  • Use case: A developer finishes a feature branch and asks for a complete PR that explains the change, links the issue, and is immediately ready for review.

Quick Start

Ask the assistant to create or update a GitHub pull request for the current branch and include the correct issue link.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a GitHub pull request from a branch diff automatically?▼

To create a GitHub pull request from a branch diff automatically, you need a tool that reads repository state, compares base-branch differences, and generates a review-ready summary with formatted issue links.

How do I link a GitHub issue to a pull request correctly?▼

Linking a GitHub issue to a pull request requires formatting issue references correctly in the PR body so close or reference behaviors trigger properly. PR generation tools format these links automatically during creation.

Can I update an existing GitHub pull request when branch changes are published?▼

Yes, you can update an existing GitHub pull request after publishing new branch changes. PR automation tools detect the published state and edit the existing PR body to reflect the latest branch diff.

What is the best way to generate a review-ready pull request body for a feature branch?▼

The best way to generate a review-ready pull request body for a feature branch is using repository-aware automation that adapts the PR template to the change type and includes issue context.

Does PR automation work with base-branch comparison templates?▼

Yes, PR automation works with base-branch comparison templates by reading the repository state and adapting the generated PR body to match the specific change type and repository conventions.

Related Skills

Explore More Software Engineering Skills→
warpdotdevwarpdotdev
292

implement-issue

Orchestrate issue-to-diff translation using local shared implementation skills.

Official
Intermediate
jitraponjitrapon
11

review-pr

Fetch and summarize GitHub pull request review comments by status.

Community
Intermediate
ayazhankadessovaayazhankadessova

fork-dev-branch

Create a Git branch named issue-<number> for a GitHub issue.

Community
Intermediate
Rune-kitRune-kit
82

git

Generate semantic commit messages and Pull Request descriptions from Git history.

Official
Advanced