Skill

Context

Commits changes to a new branch if on main, pushes to origin, creates a GitHub pull request with concise message, and enables auto-merge via GitHub CLI.

Git

Github

Bash

git-workflow

automation

npx claudepluginhub oxidian/cc-plugins --plugin oxgh

Tool Access

This skill is limited to using the following tools:

Bash(git checkout --branch:*)Bash(git checkout -b:*)Bash(git add:*)Bash(git status:*)Bash(git push:*)Bash(git commit:*)Bash(git log:*)Bash(gh pr create:*)Bash(gh pr merge:*)

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

Automates Git workflow: creates new branch if on main, commits changes with concise message, pushes, creates GitLab MR, enables auto-merge on pipeline success. Use after code changes.

9 tools

oxgl

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

Stats

Parent Repo Stars11

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Context

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

Commit and PR style

Use a short commit/PR title (one line, imperative mood) that describes WHAT changed - never meta-messages like "Address review feedback" or "Fix PR comments"
The commit/PR body should usually be blank - the code should speak for itself
ONLY add a body to explain NON-OBVIOUS changes that aren't clear from the code
AVOID summarising or describing what the code does in the PR body - that's redundant. AVOID including test plans.
If we were working on a known GitHub issue, include "Closes #ISSUE" in the PR body
See recent commits for examples (ignore dependabot and github-actions commits)

Your task

Based on the above changes:

Create a new branch if on main (do NOT add timestamps to branch names)
Create a single commit with an appropriate message
Push the branch to origin
Create a pull request using gh pr create
Enable auto-merge by running exactly gh pr merge --auto (no other flags)
You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message using separate tool calls for each command. Do NOT chain commands with && or ;. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.