A command that stages all Git changes, creates a commit, updates the project version, and pushes the work to a branch. Git is a tool for tracking code changes, while a branch is a separate line of development.

Use it to prepare and publish a feature, fix, refactor, test, documentation, or breaking change while following the project's recent commit style.

It removes several repetitive release steps and helps avoid pushing unfinished work directly from the main branch. It also keeps version numbers aligned with the type of change being committed.

quick-push — Command for Claude Code by jmagar/claude-homelab

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.

Clone the repo

git clone --depth 1 https://github.com/jmagar/claude-homelab

Made for: Claude Code.

Or install homelab-core, the plugin that ships this one along with the rest of its 18 skills, 5 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jmagar/claude-homelab/quick-push/github.svg)](https://agentmods.dev/commands/jmagar/claude-homelab/quick-push)

Your own site

<a href="https://agentmods.dev/commands/jmagar/claude-homelab/quick-push"><img src="https://agentmods.dev/badge/commands/jmagar/claude-homelab/quick-push/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jmagar/claude-homelab/quick-push"><img src="https://agentmods.dev/badge/commands/jmagar/claude-homelab/quick-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,092 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.01092
Opus 5.5	$0.00006	$0.00437
Sonnet 5.5	$0.00003	$0.00218
Haiku 4.5	$0.00002	$0.00109

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

Security

Grade A, and why

quick-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 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.

commands/quick-push.md · 95 lines

How it starts

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

Context

Current branch: !git branch --show-current
Git status: !git status --short
Remote info: !git remote -v | head -1

Your task

Work through these steps in order:

1. Orient

Check if we're on a feature branch (not main/master)
If on main/master, create a new feature branch with a descriptive name based on the changes
Run git diff --stat HEAD to understand the scope of changes
Run git log --oneline -5 to understand recent commit conventions

2. Bump version (before staging)

Detect the project type and bump the version based on the commit message you'll generate.

Bump rules (based on the commit message prefix you'll draft in step 3):

feat!: or BREAKING CHANGE → major (X+1.0.0)
feat or feat(...) → minor (X.Y+1.0)
Everything else (fix, chore, refactor, test, docs, etc.) → patch (X.Y.Z+1)

Process:

Read the current version from the primary manifest (first match: Cargo.toml, package.json, pyproject.toml)
Draft the commit message mentally (you'll finalize it in step 4)
Determine bump type from the commit prefix
Calculate the new version
Update the version in ALL of these files that exist in the repo:
- Cargo.toml — version = "X.Y.Z" in [package]
- package.json — "version": "X.Y.Z"
- pyproject.toml — version = "X.Y.Z" in [project]
- .claude-plugin/plugin.json — "version": "X.Y.Z"
- .codex-plugin/plugin.json — "version": "X.Y.Z"
- gemini-extension.json — "version": "X.Y.Z"
If Rust: run cargo check to update Cargo.lock (it records the version)
Report: Version: X.Y.Z → A.B.C (bump type) and list which files were updated

Skip conditions:

Version is 0.0.0 or 0.0.1 (project not yet versioned)
No manifest file found
The --no-bump flag was passed as a skill argument

3. Update CHANGELOG.md (before staging)

If a CHANGELOG.md exists in the repo root:

Find the most recently documented commit in the changelog (look for commit hashes in the table)
Run git log --oneline <last_documented_sha>..HEAD to get undocumented commits
If there are new commits, update the changelog:
- Add new rows to the commit summary table (newest first)
- Update the Highlights section with grouped summaries
- Keep the existing structure and style
If no CHANGELOG.md exists, skip this step

Read the full file on GitHub · 95 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.

1mo ago First seen · 95 lines · 15 tokens per session scan A 862e919b2137

Subscribe to this mod's changes

quick-push is a command published in the GitHub repository jmagar/claude-homelab (86 stars, last pushed 21d ago), licensed MIT. It adds 15 tokens to every session and 1,092 once invoked, about $0.0001 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.

Claude Code Commits Git and workflow LLM agents ai model-context-protocol self-hosted

commit

Creates commits with Conventional Commits format (feat/fix/docs/refactor/test/chore), scope detection, co-author attribution, and pre-commit hook compliance. Validates staged changes and prevents secrets or generated-only files from being committed. Use for requests to commit, stage and commit, save progress, or write…

yonatangross/orchestkit · 87 tokens

careful

Blocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE / TRUNCATE, kubectl delete and terraform or tofu destroy, including inside ssh remote commands, and makes Claude ask the…

yonatangross/orchestkit · 84 tokens

quick-push