commit-authoring

仓库创建 2026年7月26日最近提交 20 小时前SkillHot 收录 16 小时前

这个 Skill 做什么

提交代码时把一项工作的改动做成一个原子提交，方便别人 review、回滚和测试。用 Conventional Commits 格式，标题用祈使句，提交正文写为什么做而不是怎么做。好处是每个提交都是单一关注点，reviewer 不用从 diff 里猜意图，适合每次 git_commit 都遵循。

▸ 展开 SKILL.md 英文原文

How to write one atomic commit for a code change - Conventional Commits format, imperative subject, why-not-how body. Use whenever you commit code (git_commit): one node's work is exactly one reviewable, testable commit.

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/commit-authoring/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/commit-authoring/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Commit Authoring

One implementer node = **one atomic commit**. Write the commit so it reads as a single, reviewable, testable unit - and write its message so a reviewer never has to reverse-engineer intent from the diff.

## What "atomic" means (non-negotiable)

- **One concern.** A subject that needs "and" is two commits. Never mix a refactor with a behaviour change - the reviewer can't tell an intentional change from an accident of the refactor.
- **Builds and tests pass at THIS commit.** Rolling back to it leaves a working tree (bisectable, revert-safe). Your node's `checks` enforce this.
- **Under ~400 lines of diff.** Past that, review quality collapses. If the change is bigger, it's

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有