gh-create-pr

Commit unstaged changes, push the branch, and create a pull request.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/bastani-inc/atomic --skill gh-create-pr-bastani-inc
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: gh-create-pr
Source: https://github.com/bastani-inc/atomic/tree/main/.agents/skills/gh-create-pr
Command: npx skills add https://github.com/bastani-inc/atomic --skill gh-create-pr-bastani-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns unstaged work into a ready-to-review pull request, handling commit creation, branch pushing, and PR setup so you can move from local changes to collaboration without manual GitHub steps.

Core Features & Use Cases

  • Commit and organize changes using conventional commit-style messages.
  • Push the current branch safely, creating a feature branch when needed.
  • Review diffs and generate a concise PR title and description.
  • Use case: after finishing a fix, ask it to package the changes, push them, and open a PR for review.

Quick Start

Use the gh-create-pr skill to commit my current changes, push the branch, and open a pull request with a conventional title and summary.

Frequently Asked Questions about gh-create-pr

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

FAQPage Schema
How do I create a GitHub pull request from unstaged local changes?ā–¼

To create a GitHub pull request from unstaged local changes, you can use a workflow that automatically stages your work, commits it with a conventional message, pushes the branch, and generates the PR structure for review.

Can AI generate conventional commit messages and PR titles from my git diff?ā–¼

Yes, AI can review your git diff to generate conventional commit messages and structured PR titles. This process analyzes the actual code changes to ensure the commit message and PR body accurately reflect the branch updates.

What is the best way to push a feature branch and open a pull request?ā–¼

The best way to push a feature branch and open a pull request is to use an automated tool that handles branch detection, safely pushes the upstream remote, and structures the PR title and body generation without manual GitHub steps.

Does this pull request preparation workflow require manual git commands?ā–¼

No, this pull request preparation workflow does not require manual git commands. It handles diff review, branch detection, upstream push, and commit creation automatically, moving you from local changes to collaboration seamlessly.

How to update an existing pull request with new local commits?ā–¼

To update an existing pull request with new local commits, the system commits your unstaged changes, pushes the branch safely to the upstream remote, and updates the active PR with AI-assisted authorship attribution.

When do I need conventional commits for branch management?ā–¼

You need conventional commits for branch management when preparing a pull request from your current repository state. This standardizes commit creation, ensuring the feature branch updates are organized for structured code review.