Skill

push-pr

Creates new git branch if on main, commits and pushes changes, adapts PR template to git diffs, and opens GitHub pull request with conventional commit title.

Git

Github

Python

git-workflow

npx claudepluginhub rjmurillo/ai-agents

Tool Access

This skill is limited to using the following tools:

Bash(git checkout -b:*)Bash(git switch -c:*)Bash(git add:*)Bash(git status:*)Bash(git push:*)Bash(git commit:*)Bash(python3:*/pr/new_pr.py*)Bash(git diff:*)Bash(git branch:*)

Preview

- Current git status: !`git status`

SKILL.md

Similar Skills

Context

Automates Git workflow: creates new branch if on main, commits changes with short imperative message, pushes to origin, and opens GitHub PR via gh CLI. Use after code changes.

8 tools

oxgh

Context

Commits changes to a new git branch (if on main), pushes to origin, and creates or views GitHub PR with gh CLI. Activates on 'commit and push', 'open PR', 'ship it'.

8 tools

core

open-pr

1.4k

Generates GitHub PR title and description from git diff, commits, and conversation context; pushes branch and opens PR creation in browser.

4 tools

workmux-status

Stats

Parent Repo Stars26

Parent Repo Forks4

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Push PR Command

Context

Current git status: !git status

Current git diff (staged and unstaged changes): !git diff HEAD

Current branch: !git branch --show-current

Your task

Based on the above changes:

Create a new branch if on main

Determine the type of change that maps to conventional commit type followed by a 3-5 word description (e.g., fix/parser-log-enrichment)

Push the branch to origin

Read @.github/PULL_REQUEST_TEMPLATE.md

Write a new file adapting the template to describe THIS branch's changes (e.g. /tmp/PR-123-BODY.md):

Fill in all sections with actual change information from git diff
Replace placeholder comments with substantive content
Check appropriate Type of Change boxes based on actual changes
List specific files changed, test coverage added, security impacts
Do NOT leave template comments like  unfilled
Do NOT copy the template verbatim - adapt every section to your changes

Create a pull request using the new_pr skill script:

SCRIPTS_DIR="${CLAUDE_PLUGIN_ROOT:-.claude}/skills/github/scripts"
python3 "$SCRIPTS_DIR/pr/new_pr.py" --title "<conventional commit title>" --body-file /tmp/PR-123-BODY.md

Title MUST follow conventional commit format (e.g., feat: Add feature, fix(auth): Resolve bug)
Body SHOULD include GitHub issue linking keywords to auto-close issues:
- Closes #123 — auto-closes issue when PR merges
- Fixes #456 — auto-fixes issue when PR merges
- Resolves #789 — auto-resolves issue when PR merges
Ensure PR template sections are completed

You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.

Push PR Command

Context

Current git status: !git status
Current git diff (staged and unstaged changes): !git diff HEAD
Current branch: !git branch --show-current

Your task

Based on the above changes:

Create a new branch if on main
1. Determine the type of change that maps to conventional commit type followed by a 3-5 word description (e.g., fix/parser-log-enrichment)
Push the branch to origin
Read @.github/PULL_REQUEST_TEMPLATE.md
Write a new file adapting the template to describe THIS branch's changes (e.g. /tmp/PR-123-BODY.md):
- Fill in all sections with actual change information from git diff
- Replace placeholder comments with substantive content
- Check appropriate Type of Change boxes based on actual changes
- List specific files changed, test coverage added, security impacts
- Do NOT leave template comments like  unfilled
- Do NOT copy the template verbatim - adapt every section to your changes
Create a pull request using the new_pr skill script:
```
SCRIPTS_DIR="${CLAUDE_PLUGIN_ROOT:-.claude}/skills/github/scripts"
python3 "$SCRIPTS_DIR/pr/new_pr.py" --title "<conventional commit title>" --body-file /tmp/PR-123-BODY.md
```
- Title MUST follow conventional commit format (e.g., feat: Add feature, fix(auth): Resolve bug)
- Body SHOULD include GitHub issue linking keywords to auto-close issues:
  - Closes #123 — auto-closes issue when PR merges
  - Fixes #456 — auto-fixes issue when PR merges
  - Resolves #789 — auto-resolves issue when PR merges
- Ensure PR template sections are completed