commit

A guide for splitting workspace changes into focused local Git commits. Git commits are saved checkpoints of code changes, and Conventional Commits use standard prefixes such as feat or fix.

In plain words
What is it for?
It helps inspect changes, group them by purpose, create correctly named commits, run suitable checks, and confirm the final history and remaining edits.
Why use it?
It helps keep unrelated edits separate, making changes easier to review, undo, and understand without overwriting existing work.

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

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 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.00024 $0.00483
Opus 5 $0.00012 $0.00242
Sonnet 5 $0.00005 $0.00097
Haiku 4.5 $0.00002 $0.00048

Measured yesterday against content hash 703bfc65405d, 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.

.agents/skills/commit/SKILL.md · 28 lines

What it actually says

Local Commits

把当前工作区的改动按逻辑拆分为多个本地 Git commit,并保持每个 commit 可理解、可审查、可回滚。

执行规则

  1. 先读取 git status、未暂存 diff、已暂存 diff 和最近提交历史。保留用户已有改动,不使用 git reset --hardgit checkout -- 或其他破坏性操作。
  2. 按独立目的分组改动,例如功能代码、测试、文档、版本 bump、CI;不要仅按文件夹机械分组。
  3. 每组提交前检查相关文档:修改 UI、数据契约、发布流程或 Vault 语义时,把对应文档放入同一逻辑变更或单独的文档 commit。
  4. 每个 commit 只包含一个目的,使用符合 Conventional Commits 的标题,例如 feat: ...fix: ...docs: ...chore(release): bump version to ...
  5. 使用明确的文件路径或交互式 patch 精确暂存,避免把无关改动带入 commit;不要依赖 git add . 盲目提交。
  6. 每组提交前运行与该组风险匹配的最小验证;版本 bump 至少检查所有版本字段和 Cargo.lock,代码改动至少运行对应类型检查、测试或 lint。
  7. 提交后检查 git loggit status,确认 commit 顺序、标题、内容归属和剩余未提交改动都正确。
  8. 默认只创建本地 commit,不 amend、rebase、创建 tag、push 或发布 Release;这些操作必须由用户明确要求。

异常处理

  • 如果改动无法合理拆分,先说明分组方案再提交。
  • 如果存在冲突、敏感文件、生成物或无法解释的改动,停止提交相关部分并报告路径与原因。
  • 不为无关的已有改动补写说明、不重写用户提交历史。
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 · 28 lines · 24 tokens per session scan A 703bfc65405d

Subscribe to this mod's changes

commit is a skill published in the GitHub repository poco-ai/Agentero (336 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 483 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-30.