git-commit

A workflow for creating Chinese Git commit messages that follow Conventional Commits, a shared format such as feat, fix, or docs.

In plain words
What is it for?
Use it to inspect staged changes, propose a commit message, confirm the files and message, and then create the commit.
Why use it?
It reduces the effort of reviewing changes, choosing a commit type, and writing a message that accurately describes the staged files.

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

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 478 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.00025 $0.00478
Opus 5 $0.00013 $0.00239
Sonnet 5 $0.00005 $0.00096
Haiku 4.5 $0.00003 $0.00048

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

Security

Grade A, and why

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

examples/skills/git-commit/SKILL.md · 55 lines

What it actually says

格式规范

():

提交内容要求

  • 语言: 中文
  • Type: 必须是以下之一: feat, fix, docs, style, refactor, test, chore, perf, revert。
  • Subject: 使用祈使句,首字母小写,不超过 50 字,结尾不加句号。
  • Body: 详细说明变更原因。
  • 不要增加非提交信息之外信息,比如"Generated with Claude Code"
    • 比如:该消息由xxx生成.
    • 比如:Co-Authored-Byxxx.

内容依据

必须是[Changes to be committed:]里的文件

提交流程

  1. 提交前准备

    • 子代理完成当前步骤
    • 展示当前目录和分支名称
    • 拉取远程更新
    • 检测是否有冲突文件,有冲突则展示冲突列表并退出提交流程
    • 退出子代理
  2. 提交范围确认

    • 子代理完成当前步骤
    • 列出需要提交的文件列表,并展示是[新增/修改/删除],如果列表为空则向用户询问希望暂存那些文件.
    • 自动忽略 gitingore的文件
    • 用户确认后进入下一步
    • 退出子代理
  3. 生成提交信息

    • 子代理完成当前步骤
    • 查看用户确认的提交范围的文件diff
    • 生成提交信息
    • 询问用户是否修改
    • 无修改后进入下一步
    • 退出子代理
  4. 最终提交

    • 展示提交目录和分支
    • 展示提交内容
    • 用户确认后进行提交
      • 实际提交消息要保持和用户确认的字符串一致,不要增加额外内容.
    • 如果提示提交前需要拉取远程,则返回阶段1重新开始.
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 · 55 lines · 25 tokens per session scan A 5dd712922e51

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository w693847022/memory_service (1 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 478 once invoked, about $0.0001 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