openpr

Squash commits and create a pull request via GitHub CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bosmadev/claude --skill openpr-bosmadev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openpr
Source: https://github.com/bosmadev/claude/tree/main/skills/openpr
Command: npx skills add https://github.com/bosmadev/claude --skill openpr-bosmadev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create PRs by squashing commits and auto-generating a concise summary, saving time and ensuring a clean project history.

Core Features & Use Cases

  • Auto-squash commits into a single PR with a concise summary
  • Auto-generate PR body from commit messages for quick review
  • Base-branch auto-detection and safe push workflow with PR creation via GitHub CLI

Quick Start

Invoke the /openpr command to squash commits and create a pull request.

Frequently Asked Questions about openpr

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

FAQPage Schema
How do I squash commits and auto-create a pull request with a summary?

To squash commits and auto-create a pull request, you can use an automated workflow that aggregates feature branch commits, generates a concise summary from commit messages, and opens a PR via the GitHub CLI.

What is the best way to generate a PR body from commit messages?

Generating a PR body from commit messages involves consolidating multiple commits into a single documented entry. This automated summary creation extracts commit data to provide a concise overview for quick code review.

How do I automatically detect the base branch when creating a GitHub pull request?

Automatically detecting the base branch when creating a GitHub pull request is handled through base-branch auto-detection. This mechanism identifies the correct target branch before applying commit aggregation and safe push procedures.

Does the commit squash workflow require the GitHub CLI to open pull requests?

Yes, the commit squash workflow requires the GitHub CLI to create pull requests. PR creation is executed directly through the GitHub CLI as part of its safe push procedure and automated summary generation.

When should I use an automated squash commit workflow for feature branches?

You should use an automated squash commit workflow for feature branches when you need to streamline code reviews. It applies commit aggregation to consolidate multiple entries into a single, well-documented pull request for a clean project history.