git-commit-push-pr

git-commit-push-pr is a skill for Claude Code from charlesjones-dev/claude-code-plugins-dev. It costs 43 tokens per session (1,086 once invoked), scanned A, original, MIT.

A guided Git workflow that commits changes, pushes the branch, and opens a pull request, a proposal for merging code into a shared branch.

In plain words
What is it for?
Checking the current branch and changes, creating or selecting a working branch, committing, pushing, and creating a pull request.
Why use it?
It combines the routine shipping steps and asks where the work should go before making branch changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Part of the ai-git plugin — 4 skills shipped together

Good fit Checking the current branch and changes, creating or selecting a working branch, committing, pushing, and creating a pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add charlesjones-dev/claude-code-plugins-dev --skill git-commit-push-pr
Clone the repo
git clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-dev

Made for: Claude Code.

Or install ai-git, the plugin that ships this one along with the rest of its 4 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for git-commit-push-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr/github.svg)](https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr)
Your own site
<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for git-commit-push-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/git-commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,086 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01086
Opus 5.5 $0.00017 $0.00434
Sonnet 5.5 $0.00009 $0.00217
Haiku 4.5 $0.00004 $0.00109

Measured 1mo ago against content hash b66bc599214d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-commit-push-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/ai-git/skills/git-commit-push-pr/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/git-commit-push-pr - Commit, Push, PR

You are a shipping assistant. Your job is to get the current branch shipped by committing, pushing, and opening a PR. Use AskUserQuestion for all user prompts so the flow is fast with minimal typing.

Process

Step 1: Branch + Commit

First, determine the current branch:

git branch --show-current

Then run git status (never -uall) and git diff to understand changes. If there are no changes, tell the user and stop.

Branch prompt: Use AskUserQuestion to ask the user where to commit:

  • If on main or master: Do NOT allow committing directly. Present options:

    • "Create new branch" (description: "Create a feature/fix branch for these changes")
    • The user picks "Other" to type a custom branch name
  • If on any other branch (staging, feature/, fix/, etc.): Present options:

    • "Current branch ({branch_name})" (description: "Commit directly to {branch_name}") - mark as first/recommended option
    • "Create new branch" (description: "Create a new branch off {branch_name} for these changes")

If the user chooses "Create new branch" or types a custom name via "Other":

  1. Create and checkout the new branch: git checkout -b <branch_name>

Then proceed with the commit:

  1. Run git log --oneline -5 to match the repo's commit message style
  2. Stage relevant files (prefer specific files over git add -A)
  3. Draft a concise commit message focused on the "why"
  4. Create the commit with no Claude attribution — do not add any Co-Authored-By or "Generated with Claude Code" trailers
  5. Use a HEREDOC for the commit message to ensure proper formatting

Step 2: Push

  1. Check if the current branch tracks a remote: git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
  2. Push to remote with -u flag if no upstream is set, otherwise a normal push
  3. Verify the push succeeded

Step 3: Create PR

First, gather context:

# Current branch
git branch --show-current

# Check if staging exists on origin
git ls-remote --heads origin staging

# Check if main exists on origin
git ls-remote --heads origin main

Read the full file on GitHub · 119 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 119 lines · 43 tokens per session scan A b66bc599214d

Subscribe to this mod's changes

git-commit-push-pr is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 1,086 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

changelog

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

Donchitos/Claude-Code-Game-Studios · 22 tokens

comet-safe-delivery

A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.

rpamis/comet · 78 tokens

git-workflow

Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.

jezweb/claude-skills · 52 tokens

git-push

A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.

yunshu0909/yunshu_skillshub · 223 tokens

close-task-commit-push-pr

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.

devoxx/DevoxxGenieIDEAPlugin · 64 tokens