Slash Command

/SKILL

Validates local changes, commits with repo-appropriate message, pushes current branch, creates or updates PR via GitHub CLI, and optionally enables automerge.

Git

Github

git-workflow

npx claudepluginhub kaeawc/auto-mobile --plugin auto-mobile

Details

Namespacepush-pr/

Prompt Preview

# Push PR

Use this when local work is ready to publish.

- Prefer `push-pr` for one branch or one PR.
- Prefer `push-my-prs` only when the user wants a batch loop across many PRs.

## Workflow

1. Inspect `git status --short`, `git diff --stat`, and recent commit style before drafting a commit.
2. Run the relevant validation before pushing.
3. Commit intentionally with a repository-appropriate message.
4. Push the current branch, setting upstream if needed.
5. If no PR exists, create one with `gh pr create` and a body file such as `scratch/pr-body.md`.
6. If a PR already exists, update it ...

Command Content

Other plugins with /SKILL

/pr

263

Commits uncommitted changes, pushes current branch to remote, and creates GitHub Pull Request with generated title/body from commits. Returns PR URL.

6 tools

/prp-pr

173.8k

Creates GitHub PR from current branch with unpushed commits. Discovers templates, analyzes changes/files, pushes branch, fills body. Optional base-branch (default: main).

everything-claude-code

/push-pr

Commits changes to a new branch if on main, pushes to origin, fills PR template with git diff details, and opens GitHub pull request.

9 tools

project-toolkit

/commit-push-pr

18.3k

Commits current changes (staged/unstaged) to a new branch if on main, pushes to origin, and creates a GitHub pull request via gh.

6 tools

commit-commands

/SKILL

512

Configures Git user identity and project commit scopes: verifies name/email, initializes git-agent, validates scopes from .git-agent/config.yml, generates .claude/git.local.md.

haiku7 tools

git

/SKILL

512

Launches isolated code-context researcher agent to fetch repo/library context via DeepWiki, Context7, Exa, git clone, or all methods. Accepts repo URL/name and optional --method flag.

code-context

Stats

Stars34

Forks0

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Push PR Use this when local work is ready to publish. - Prefer `push-pr` for one branch or one PR. - Prefer `push-my-prs` only when the user wants a batch loop across many PRs. ## Workflow 1. Inspect `git status --short`, `git diff --stat`, and recent commit style before drafting a commit. 2. Run the relevant validation before pushing. 3. Commit intentionally with a repository-appropriate message. 4. Push the current branch, setting upstream if needed. 5. If no PR exists, create one with `gh pr create` and a body file such as `scratch/pr-body.md`. 6. If a PR already exists, update it ...

Push PR

Use this when local work is ready to publish.

Prefer push-pr for one branch or one PR.

Prefer push-my-prs only when the user wants a batch loop across many PRs.

Workflow

Inspect git status --short, git diff --stat, and recent commit style before drafting a commit.

Run the relevant validation before pushing.

Commit intentionally with a repository-appropriate message.

Push the current branch, setting upstream if needed.

If no PR exists, create one with gh pr create and a body file such as scratch/pr-body.md.

If a PR already exists, update it as needed with gh pr edit.

Enable automerge only when that matches the branch’s intended workflow.

Repo Rules

Use github-cli, gh-pr-workflow, and validate conventions.

Never use destructive git commands.

Do not skip validation unless the user explicitly accepts the risk.

Prefer squash automerge unless the repo or existing PR says otherwise.

Push PR

Use this when local work is ready to publish.

Prefer push-pr for one branch or one PR.
Prefer push-my-prs only when the user wants a batch loop across many PRs.

Workflow

Inspect git status --short, git diff --stat, and recent commit style before drafting a commit.
Run the relevant validation before pushing.
Commit intentionally with a repository-appropriate message.
Push the current branch, setting upstream if needed.
If no PR exists, create one with gh pr create and a body file such as scratch/pr-body.md.
If a PR already exists, update it as needed with gh pr edit.
Enable automerge only when that matches the branch’s intended workflow.

Repo Rules

Use github-cli, gh-pr-workflow, and validate conventions.
Never use destructive git commands.
Do not skip validation unless the user explicitly accepts the risk.
Prefer squash automerge unless the repo or existing PR says otherwise.