simple-pr

Create a GitHub pull request from staged changes with an auto-generated commit message.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/syncable-dev/tantivy --skill simple-pr-syncable-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simple-pr
Source: https://github.com/syncable-dev/tantivy/tree/main/.claude/skills/simple-pr
Command: npx skills add https://github.com/syncable-dev/tantivy --skill simple-pr-syncable-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically convert staged changes into a clean pull request by generating a concise commit message and creating a feature branch.

Core Features & Use Cases

  • Auto-generates a concise commit message describing why changes were made.
  • Creates a short, descriptive branch name based on the changes and user identity.
  • Pushes the branch and opens a PR on GitHub via gh.

Quick Start

Create a PR from your staged changes on main with an auto-generated commit message.

Frequently Asked Questions about simple-pr

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

FAQPage Schema
How do I create a pull request from staged changes with an auto-generated commit message?

To create a pull request from staged changes, this Skill automates committing, branch creation, and pushing. It generates a concise commit message and feature branch name based on your changes and user identity, then opens the PR on GitHub via gh.

Do I need the GitHub CLI to automate opening a pull request from my local repository?

Yes, automating opening a pull request requires the GitHub CLI (gh) and a Git environment. The Skill uses gh to push your feature branch and open the PR directly on GitHub after validating the main branch.

Can I automatically generate a branch name based on my staged Git changes?

Yes, you can automatically generate a branch name based on staged Git changes. The Skill creates a short, descriptive branch name using the content of your changes combined with your configured git user.name.

What is the best way to standardize commit messages for small changes in collaborative reviews?

The best way to standardize commit messages for small changes is using this automation Skill. It auto-generates a concise commit message describing why changes were made, ensuring consistent formatting across collaborative reviews without manual effort.

Why does creating a pull request automatically require validating the main branch?

Creating a pull request automatically requires validating the main branch to ensure your feature branch is created from the correct baseline. This prevents integration issues and ensures the auto-generated PR targets the proper repository branch.