Verified:GitHub

pr

Create or update GitHub and GitLab pull requests from branch commits and diffs.

10|5|Updated Mar 3, 2026

Search Tags:#code review #pull request #git workflow #conventional commits #github #gitlab #merge request

One-click install

npx skills add https://github.com/JHostalek/dotclaude --skill pr-jhostalek

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/pr
Command: npx skills add https://github.com/JHostalek/dotclaude --skill pr-jhostalek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents incomplete, duplicated, or poorly documented pull requests by grounding the review body in the actual branch history and diff.

Core Features & Use Cases

Preflight Validation: Inspects committed changes, checks for existing pull requests, pushes the branch, and sets its upstream before invoking a CLI.
PR/MR Creation and Updates: Supports GitHub and GitLab workflows, including draft status, conventional titles, cleanup flags, and body updates.
Reviewer-Focused Documentation: Produces compact summaries, witnessed verification details, review notes, residual risks, and architecture diagrams when the change warrants them.
Use Case: When a feature branch is ready for review, use the skill to create or update the appropriate pull request with an accurate title, concise body, verification status, and merge cleanup configuration.

Quick Start

Ask the skill to create or update a review-ready pull request for the current branch.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I create a review-ready pull request from my current git branch?▼

To create a review-ready pull request, the skill analyzes your branch's actual commits and diff to generate an accurate title and reviewer-focused body. It performs preflight validation, pushes the branch upstream, and invokes the available gh or glab CLI to submit the request.

Does this pull request generator work with both GitHub and GitLab workflows?▼

Yes, this pull request generator supports both GitHub and GitLab workflows by utilizing the gh and glab CLI tools. It creates or updates merge requests and pull requests while applying preflight checks, draft decisions, and reviewer-focused descriptions across both platforms.

What is the best way to write a pull request description from existing conventional commits?▼

The best way to write a pull request description from conventional commits is to ground the text in the actual branch history and diff. This skill produces compact summaries, review notes, residual risks, and verification details to prevent poorly documented requests.

Can I update an existing pull request without creating a duplicate merge request?▼

Yes, you can update an existing pull request without creating a duplicate. The preflight validation checks for existing requests on the current branch, allowing the skill to safely update the body, apply conventional titles, set draft status, and configure merge cleanup flags.

What do I need in my repository environment before generating a merge request with this tool?▼

Before generating a merge request, you need repository context, a configured remote, and an available gh or glab CLI. The environment must also include witnessed verification information so the skill can accurately report preflight checks and push the branch upstream.

Why does my automated pull request fail preflight validation before pushing upstream?▼

Automated pull request preflight validation fails if committed changes are incomplete or repository context is missing. The skill inspects the branch history and diff before attempting an upstream push, ensuring the configured remote and CLI environment are fully prepared to prevent invalid requests.