open-pr

Create or update GitHub pull requests with semantic titles and template-aligned descriptions.

8|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/hutchic/.cursor --skill open-pr-hutchic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/hutchic/.cursor/tree/main/.cursor/skills/git/open-pr
Command: npx skills add https://github.com/hutchic/.cursor --skill open-pr-hutchic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and updating GitHub pull requests efficiently requires crafting concise, semantic titles and keeping PR descriptions aligned with project templates. This reduces back-and-forth and helps reviewers understand changes at a glance.

Core Features & Use Cases

  • Generate a terse semantic PR title based on commits and branch name, or update an existing PR's title if needed.
  • Automatically align the PR body with the repository's PR template, ensuring required sections are present (Description, Type of Change, Testing, Checklist).
  • Detect existing PRs for the head branch and apply the Update Flow, otherwise create a new PR with MCP or gh CLI.

Quick Start

Create or update a PR from the current branch to the target base branch using a concise, semantic title and a template-aligned description.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with semantic titles?

Automating GitHub pull request creation involves generating a terse semantic title from commits and branch names, then aligning the PR body with repository templates using GitHub MCP or gh CLI to ensure required sections are present.

Can I update an existing GitHub pull request automatically when pushing new commits?

Yes, you can update an existing GitHub pull request automatically by detecting an open PR for the head branch and applying an update flow to reflect the latest changes and refine the semantic title.

Do I need GitHub CLI or MCP access to open pull requests with semantic titles?

Yes, you need GitHub access via either the MCP server or gh CLI to open or update pull requests, along with a ready branch to operate on and ensure the description matches project templates.

What's the best way to align a pull request description with a repository template?

The best way to align a pull request description with a repository template is to automatically parse the project's required sections like Description, Type of Change, Testing, and Checklist, ensuring the PR body matches the expected format.

How does generating a semantic PR title from commit history work?

Generating a semantic PR title from commit history works by analyzing the pushed commits and branch name to craft a terse, conventional-like title format that helps reviewers understand the changes at a glance.

Why does my pull request title not match the project's conventional format?

Your pull request title may not match the conventional format because it lacks semantic structure derived from commits. Enforcing a conventional-like title format based on branch names and commit history resolves this issue.