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.
npx agentmods add skills/qiniu/go-sdk/git-commitnpx skills add qiniu/go-sdk --skill git-commitgit clone --depth 1 https://github.com/qiniu/go-sdkWhat 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 | $0.00053 | $0.01310 |
| Opus 5 | $0.00026 | $0.00655 |
| Sonnet 5 | $0.00011 | $0.00262 |
| Haiku 4.5 | $0.00005 | $0.00131 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
规范化提交
开始时声明:"我正在使用 git-commit skill 生成并提交规范化 commit。"
快速开始
- 查看
status/diff/log,确认提交范围与语言风格。 - 暂存目标文件并展示"将提交列表"。
- 生成符合 Angular 规范的 commit message。
- 提交后如有上游分支则 push。
何时不要使用(Do NOT use)
- 工作区无待提交变更。
- 用户仅请求代码分析/评审,不需要提交。
- 用户明确要求仅生成建议,不执行
git commit。
触发样例与非样例
- 应触发:
- "帮我按 Angular 规范提交这些改动。"
- "写一个 commit message 并 push。"
- 不应触发:
- "review 这个 PR 有没有问题。"
- "分析下这个报错根因。"
使用示例
# 基本提交
git-commit 修复上传逻辑
# 提交并 push
git-commit push=true
预检查命令
git status --short
git diff HEAD
git branch --show-current
git log --oneline -10
消息规范
Header:<type>(<scope>): <summary>
Type:
feat新功能fix缺陷修复docs文档改动refactor重构perf性能优化test测试相关chore杂项维护style代码格式调整
Scope 建议值(本项目常用):
storage/storagev2/auth/cdn/pili/rtc/sms/linking/qvsiam/media/audit/sandboxclient/conf/reqidinternal/examples
Summary 规则:祈使句、现在时、首字母小写、不加句号。
Body 规则:
docs可省略,其他类型建议必须有- 至少说明"为什么改"与"影响范围"
- 非
docs类型时,body 至少 20 个字符 - 单段 body 不超过 3 行,保持简洁
Footer(按需):
BREAKING CHANGE: ...Fixes #123/Closes #456
语言规则
- 参考最近 10 条提交语言。
- 近期中文为主则用中文;近期英文为主则用英文。
执行流程
- 先确认提交文件列表。
- 执行
git add(按文件名添加,避免git add -A)。 - 展示 commit message 草案并确认。
- 执行
git commit。 - 如有上游分支则 push:
git push- 或
git push -u origin <current-branch>
提交前检查提醒
提交代码前提醒用户确认已通过:
make unittest— 单元测试make staticcheck— 静态检查gofmt -s -w .— 代码格式化
如果是生成代码相关修改,还需确认已运行 make generate。
关键约束
- 不要使用 emoji 在 commit message 中
- 不要在 commit message 中包含 AI 辅助工具相关信息
- 不要添加 "Generated with" 或 "Co-Authored-By: AI" 等内容
- 不要使用
--no-verify跳过 hooks
输出模板
已提交: <commit-hash>
标题: <type(scope): summary>
分支: <branch>
Push: 成功/失败/未执行
失败回退
- 工作区无变更:输出
git status结果,提示无可提交内容。 git commit失败(hook 报错):输出完整报错,建议修复后重试,不跳过 hook。git push失败(远端冲突):输出报错,建议先 pull/rebase 再重试。
验收标准(统一)
- 输入前提:参数与上下文可解析;缺省参数按 skill 默认值执行,并在输出中注明。
- 产出要求:按 skill 约定的输出模板给出结果,并包含关键证据(命令、路径、链接或日志摘要)。
- 通过判定:主流程步骤已完成且无阻塞;若有未完成项,必须明确标注影响范围与下一步。
- 默认策略(非交互):需要确认但用户未及时响应时,采用"推荐默认值/最小风险项"继续;需要交互选择时优先推荐项。
- 阻塞升级:遇到权限、凭证、外部依赖缺失时立即停止该步骤,输出"阻塞点 + 已尝试 + 需要用户提供的信息"。
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.
- 2d ago First seen · 149 lines · 53 tokens per session scan A e3da5b66fa9d
git-commit is a skill published in the GitHub repository qiniu/go-sdk (157 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,310 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…