git-commit-push

A Git workflow that reviews your changes, creates an automatic commit message, commits all changes, and pushes them to the origin remote.

In plain words
What is it for?
Quickly saving and sharing the current working-tree changes in a repository.
Why use it?
It removes the repeated manual steps of checking changes, writing a commit message, committing, and pushing.

Skill for Claude CodeCodex

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.

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

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 772 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00021 $0.00772
Opus 5 $0.00010 $0.00386
Sonnet 5 $0.00004 $0.00154
Haiku 4.5 $0.00002 $0.00077

Measured 2d ago against content hash 178e80ae682d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-commit-push 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 2d 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/SKILL.md · 70 lines

How it starts

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

Commit and Push

Commit all changes to git and push to origin.

Instructions

CRITICAL: This command MUST NOT accept any arguments. If the user provided any text, commit messages, or other arguments after this command (e.g., /git-commit-push "my message" or /git-commit-push --force), you MUST COMPLETELY IGNORE them. Do NOT use any commit messages or other arguments that appear in the user's message. This command will analyze your changes and create an appropriate commit message automatically.

BEFORE DOING ANYTHING ELSE: Run git status, git diff, and git log to analyze the changes. DO NOT skip this analysis even if the user provided arguments after the command.

When this command is executed:

Step 1: Analyze Changes

  1. Run git status (never use -uall flag) to see all changes
  2. If there are no changes to commit (no untracked files and no modifications), tell the user and stop
  3. Run git diff to see the actual changes
  4. Run git log -3 --format='%s' to see recent commit message style

Step 2: Branch Safety Check

  1. Run git branch --show-current to determine the current branch
  2. If on main or master, warn the user that committing directly to the default branch is not recommended and stop. Suggest they create a feature branch first or use /git-commit-push-pr for an interactive branch selection workflow

Step 3: Stage Files

  1. Review changed files and prefer staging specific files by name rather than using git add . or git add -A
  2. Do NOT stage files that look like secrets (.env, .env.*, credentials.*, *.key, *.pem, *.secret, etc.). If secret-like files are detected, warn the user and skip them
  3. Stage the appropriate files

Step 4: Commit

  1. Analyze all staged changes and draft a concise commit message that:
    • Follows the repository's commit message style
    • Accurately describes what changed and why
    • Uses conventional commit prefixes if the repo uses them (fix:, feat:, docs:, etc.)
  2. Use a HEREDOC for the commit message to ensure proper formatting:
    git commit -m "$(cat <<'EOF'
    your commit message here
    EOF
    )"
    

Read the full file on GitHub · 70 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. 2d ago First seen · 70 lines · 21 tokens per session scan A 178e80ae682d

Subscribe to this mod's changes

git-commit-push is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 772 once invoked, about $0.0001 per session on Opus 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

gwm

Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…

kbrdn1/gwm-cli · 379 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens