commit

A Git workflow that stages selected files and creates a local commit after the code has passed review. Git is a tool for tracking changes to code.

In plain words
What is it for?
Use it to inspect changed files, stage only the intended ones, write a commit message, create the commit, and confirm the resulting commit and workspace status.
Why use it?
It helps avoid committing unrelated files or sensitive files such as environment settings. It also checks that a review was completed and reports whether the commit succeeded.

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/zhangshenao/harness9/commit
Any agent
npx skills add ZhangShenao/harness9 --skill commit
Clone the repo
git clone --depth 1 https://github.com/ZhangShenao/harness9

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 590 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.00035 $0.00590
Opus 5 $0.00017 $0.00295
Sonnet 5 $0.00007 $0.00118
Haiku 4.5 $0.00003 $0.00059

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

Security

Grade A, and why

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

skills/commit/SKILL.md · 79 lines

What it actually says

commit — Stage & Commit

Overview

在 Code Review 通过后,将有效的代码变更暂存并提交到本地 Git 仓库。

前置条件检查

  1. 确认本次对话中已执行过 /cr(Code Review)
  2. 若 Review 报告存在 Critical 问题,停止执行,提示用户先修复
  3. 若未执行过 /cr,先调用 cr skill 完成 Review,再继续

执行步骤

1. 确认变更范围

git status
git diff --stat
git diff --cached --stat

2. 精确暂存文件

不使用 git add -Agit add .,逐文件或逐目录添加:

git add <具体文件或目录>

排除规则:

  • .env、包含敏感信息的文件 → 不暂存,提示用户确认
  • 与本次功能无关的临时文件 → 不暂存

3. 起草提交信息

参考以下格式(优先遵循仓库现有风格,通过 git log --oneline -10 判断):

<type>: <简明描述>(50 字符以内)

<可选正文:说明 why,不是 what>

常用 typefeat / fix / docs / refactor / test / chore

禁止在提交信息中添加任何 AI 工具相关的署名,例如 Co-Authored-By: Claude 或类似内容。

4. 执行提交

git commit -m "$(cat <<'EOF'
<提交信息>
EOF
)"

5. 确认结果

git log --oneline -3   # 确认提交已记录
git status             # 确认工作区干净

输出提交的 hash 与摘要,告知用户提交成功。

常见错误

问题 处理
pre-commit hook 失败 修复 hook 报告的问题,重新 git add 后创建 commit,不使用 --amend
暂存了不该提交的文件 git restore --staged <file> 取消暂存,重新操作
工作区已无变更 告知用户没有可提交的内容
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 · 79 lines · 35 tokens per session scan A c960915e2c5d

Subscribe to this mod's changes

commit is a skill published in the GitHub repository ZhangShenao/harness9 (135 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 590 once invoked, about $0.0002 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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens