commit

A Git commit workflow for grouping related changes, staging only the intended files, and writing a repository-consistent message. Git is the version-control system that records project changes.

In plain words
What is it for?
Use it to inspect the workspace, split changes into sensible commits, choose files to stage, write the commit message, and verify the final status.
Why use it?
It reduces the risk of combining unrelated work, committing secrets, or creating confusing history. It also reminds you to check what remains uncommitted afterward.

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

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 835 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.00045 $0.00835
Opus 5 $0.00023 $0.00417
Sonnet 5 $0.00009 $0.00167
Haiku 4.5 $0.00005 $0.00084

Measured yesterday against content hash 0e44d62a52c5, 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 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.

crates/riot-kernel/builtin/skills/commit/SKILL.md · 81 lines

What it actually says

提交改动

先看清全貌,再决定分几个提交

并行跑这三条,不要只看 git status

git status --short
git diff --stat
git log --oneline -10

git log 那条是为了照着这个仓库的习惯来:标题用什么语言、有没有 feat: 这类前缀、正文写多细、提交粒度是大批次还是一改一提。不同仓库 差别很大,猜错的表现是这个提交在历史里读起来像外来的。

判据是能不能用一句话说清这批改动解决了什么问题。能,就是一个提交; 需要用「以及」连接两件无关的事,就该切开。

只暂存这一组

[约束] 不要 git add -Agit add .,除非你已经确认工作区里只有 这一件事。工作区经常同时挂着几个主题的改动(有些还是用户自己没提完的), 全加进去就把无关的东西一起提了,而那之后再拆得动历史。

逐个文件或逐个目录加,然后确认一遍暂存区:

git add path/to/a path/to/b
git status --short          # 前缀 M/A 的那些就是这次要提的

别带上不该带的

  • 密钥与凭证:.env*.pemauth.json、任何含 token 的文件。 用户明确要求提交这类文件时,先提醒他一次。
  • 生成物不一定该跳过。有些仓库把生成的类型、schema、lockfile 检入版本库并在 CI 里校验同步 —— 那种情况下漏掉它们会让 CI 直接红。 不确定就看 .gitignore 和 CI 配置,别按直觉判断。

消息

标题一行说清这批做了什么,语言和格式跟着 git log 里的既有风格。

正文写为什么,不是罗列做了什么 —— 做了什么看 diff 就有,而 「为什么这么做、为什么不用另一条路」只有现在写下来。特别值得写的:

  • 不选另一条方案的理由;
  • 踩过的坑和它的具体症状(「表现是按了没反应」比「修复了事件问题」 有用得多);
  • 这次改动依赖或守住了什么约束,破了会怎样。

用 HEREDOC 传消息,保证换行不被吃掉:

git commit -m "$(cat <<'EOF'
标题

正文段落。

EOF
)"

提交之后

跑一次 git status 确认干净,并把结果告诉用户 —— 包括没提交的那些还留在 工作区,那是他接着要处理的。

不要做的事

  • 不要 git push、切分支、stashreset --hard,除非用户明确要求。
  • 不要 --amend,除非用户明确要求、那个提交是本次对话里刚做的、而且还没推。
  • 提交被 pre-commit hook 拒了:修问题再提一个新的提交,不要 amend。
  • 没有改动就不要造一个空提交。
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 · 81 lines · 45 tokens per session scan A 0e44d62a52c5

Subscribe to this mod's changes

commit is a skill published in the GitHub repository caiwuu/Riot (2 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 835 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-31.

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