A workflow for committing code changes, sending them to a remote repository, and opening or reusing a pull request, which is a proposed change for review.

Use it after making changes when they need to be committed, pushed, and prepared for review. It can also handle an optional merge after the pull request is ready.

It organizes the final delivery steps and checks whether required tests or documentation are missing before proceeding.

commit-push — Skill for Claude Code and Codex by nirecom/agents

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 nirecom/agents --skill commit-push

Clone the repo

git clone --depth 1 https://github.com/nirecom/agents

Made for: Claude Code, Codex.

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/skills/nirecom/agents/commit-push/github.svg)](https://agentmods.dev/skills/nirecom/agents/commit-push)

Your own site

<a href="https://agentmods.dev/skills/nirecom/agents/commit-push"><img src="https://agentmods.dev/badge/skills/nirecom/agents/commit-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/skills/nirecom/agents/commit-push"><img src="https://agentmods.dev/badge/skills/nirecom/agents/commit-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,510 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.00020	$0.01510
Opus 5.5	$0.00008	$0.00604
Sonnet 5.5	$0.00004	$0.00302
Haiku 4.5	$0.00002	$0.00151

Measured yesterday against content hash 690c2519a00c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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.

skills/commit-push/SKILL.md · 92 lines

How it starts

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

Commit staged/unstaged changes, push to the remote, and open or reuse a PR.

Pre-commit check

If tests are missing or the commit hook blocks due to missing tests:

Never write tests directly in this conversation.
Invoke the /write-tests skill first, then resume commit-push.

If documentation is missing or the commit hook blocks due to missing documentation updates:

Invoke the /update-docs skill first, then resume commit-push.

Phase 1 (issue-close-stage) pre-flight

Run: bash "$AGENTS_MAIN_ROOT/bin/detect-non-github.sh" "Phase 1 pre-flight" || NON_GITHUB=1

When NON_GITHUB=1 (non-GitHub remote): skip the entire pre-flight block below (including check-phase1-complete.sh), then proceed with commit/push as normal — do NOT abort the skill. When the command exits 0 (GitHub remote, or unknown/fail-open): run the pre-flight as normal.

Skip message on non-GitHub remote (emitted by the script to stdout): [GITHUB_ISSUES disabled: non-GitHub remote detected, skipping Phase 1 pre-flight]

For each issue N in the session's closes_issues list (the JSON array printed by node "$AGENTS_MAIN_ROOT/bin/parse-closes-issues" --session <session-id> — do not reimplement), run from the worktree root:

bash "$AGENTS_MAIN_ROOT/bin/github-issues/check-phase1-complete.sh" <N>

Non-zero → abort /commit-push and surface stderr (it names the missing condition: sentinel, history entry, or both). Resolve by invoking /issue-close-stage <N> from the linked worktree, then re-run /commit-push.

Skip this pre-flight when:

closes_issues is empty, or the session intent file is missing.
Running from the main worktree (main-worktree commit-push is only valid when ENFORCE_WORKTREE=off, where the 2-phase split does not apply).

Procedure

Read rules/github-issues.md before CP-1 — on-demand-only, never auto-injected. Read rules/coding.md before CP-2 — on-demand-only, never auto-injected; its Public GitHub Rules govern the commit message and PR body.

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

yesterday Changed · -1 lines 690c2519a00c
8d ago Changed · -28 lines · +2 tokens per session 93b3f2b0c43a
9d ago Changed c6d8288b262d
10d ago Changed 69fe5b92bfa8
12d ago Changed b7583bd4189c
22d ago Changed 01312626abb2
1mo ago Changed b205e5f64feb
1mo ago Changed 2f6b3cee3f71
1mo ago Changed bf01c1f77c11
1mo ago First seen · 121 lines · 18 tokens per session scan A 961ecbc721f6

Subscribe to this mod's changes

commit-push is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,510 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-31.

Commits Git and workflow

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

davidondrej/skills · 25 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens