commit
Commit work in a tree another session may be using. Use before any git commit.
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- commit
- description
- Commit work in a tree another session may be using. Use before any git commit.
03 SKILL.md 正文
Invoker precedence. If Chrispian's instruction contradicts a default here, they win.
The form
git commit -m "<message>" -- <path> [<path>...]
Name the paths you mean. This builds the tree from HEAD plus exactly what you
name and leaves the index untouched — which is what makes it safe when another
session shares the working tree.
Flags go before the --. Everything after it is read as a pathspec.
Before
git status --short— know what is yours and what arrived from elsewhere.git diff --cachedif the index matters to you.
The message
Say what changed and why it changed. The subject is the claim; the body is the evidence. If the commit carries a measurement, carry the command that produced it beside the number.
04 同仓库更多 Skills
tangent
Open a browser workflow when chat is the wrong shape for structured input — triaging many items with one decision, multi-question feedback, or design review. Requires the Tangent MCP server.
release
Cut a release. Use before git tag or gh release create.
push
Push work off this machine. Use before any git push.
pull-request
Open a pull request. Use before gh pr create.
end-of-session
Wrap up a work session — reconcile the git tree, commit what this session authored, review drafts, and capture durable signal. Use when the user signals the session is ending.
capture-limitation
Record a known limitation, preserved tech debt, or a scope fence with its rationale to Tesseract. Use when a change deliberately does not fix something, or a "## Known limitations" / "## Out of scope" section lands in a tracking file.