commit-push

A command template for committing the current branch's changes and pushing them to a remote Git repository. Git is a tool for tracking code changes, while a branch is a separate line of work.

In plain words
What is it for?
Use it after making changes when you need to commit them and send the current branch to the configured remote named origin.
Why use it?
It groups branch checks, optional quality checks, staging, committing, and pushing into one repeatable workflow.

Command for Cursor

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 commands/kinopeee/cursorrules/commit-push
Clone the repo
git clone --depth 1 https://github.com/kinopeee/cursorrules

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 825 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.00000 $0.00825
Opus 5 $0.00000 $0.00413
Sonnet 5 $0.00000 $0.00165
Haiku 4.5 $0.00000 $0.00082

Measured yesterday against content hash 6014db46a9d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

.cursor/commands/commit-push.md · 84 lines

What it actually says

コミット&プッシュ(現在のブランチ)

概要

現在のブランチに対して変更をコミットし、リモートへプッシュするための汎用的なコマンド例です。
main/master への直接プッシュ禁止や、コミット前に実行する品質チェック(lint / test / build など)は、各プロジェクトのポリシーに応じてこのテンプレートを調整してください。

前提条件

  • 変更済みファイルが存在すること
  • リモート origin が設定済みであること

実行手順(対話なし)

  1. ブランチ確認(main/master 直プッシュ防止)
  2. 必要に応じて品質チェック(lint / test / build など)を実行
  3. 変更のステージング(git add -A
  4. コミット(引数または環境変数のメッセージ使用)
  5. プッシュ(git push -u origin <current-branch>

使い方

A) 安全な一括実行(メッセージ引数版)

MSG="<Prefix>: <サマリ(命令形/簡潔に)>" \
BRANCH=$(git branch --show-current) && \
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then \
  echo "⚠️ main/master への直接プッシュは禁止です"; exit 1; \
fi

# 任意の品質チェック(必要な場合のみ)
# 例:
# ./scripts/lint.sh && ./scripts/test.sh && ./scripts/build.sh || exit 1

git add -A && \
git commit -m "$MSG" && \
git push -u origin "$BRANCH"

例:

MSG="fix: 不要なデバッグログ出力を削除" \
BRANCH=$(git branch --show-current) && \
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then \
  echo "⚠️ main/master への直接プッシュは禁止です"; exit 1; \
fi

# 任意の品質チェック(必要な場合のみ)
# ./scripts/quality-check.sh || exit 1

git add -A && git commit -m "$MSG" && git push -u origin "$BRANCH"

B) ステップ実行(読みやすさ重視)

# 1) ブランチ確認
BRANCH=$(git branch --show-current)
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
  echo "⚠️ main/master への直接プッシュは禁止です"; exit 1;
fi

# 2) 任意のローカル品質チェック(必要に応じて追加)
# 例:
# echo "品質チェック実行中..."
# ./scripts/lint.sh && ./scripts/test.sh && ./scripts/build.sh || exit 1

# 3) 変更をステージング
git add -A

# 4) コミット(メッセージを編集)
git commit -m "<Prefix>: <サマリ(命令形/簡潔に)>"

# 5) プッシュ
git push -u origin "$BRANCH"

ノート

  • コミットメッセージのフォーマットやメッセージ生成の原則は、.cursor/rules/commit-message-format.mdc などの規約に従ってください。
  • 先に git statusgit diff で差分を確認してからの実行を推奨します。
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. yesterday First seen · 84 lines · 0 tokens per session scan A 6014db46a9d8

Subscribe to this mod's changes

commit-push is a command published in the GitHub repository kinopeee/cursorrules (1,116 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 825 tokens. 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.