commit
Use when committing or pushing changes to the repository.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- commit
- description
- Use when committing or pushing changes to the repository.
03 SKILL.md 正文
<straw-dog question="q-yiygh6">Mechanism: not yet</straw-dog>
-
Look at pending changes; group them by content aligning with origin topic, ticket, rfc or change type (documentation, code, CI, skills).
-
Separate implementation and documentation commits.
-
Write the subject in the project's convention: the one it states, else the one its tooling enforces, else the one its recent history keeps; a project with none of these, Conventional Commits.
-
In case the file changes belong to several groups, commit the file with the group forming its dominant topic and mention the bleed in that commit's message.
-
Do not reference sessions in commit comments, sessions are ephemeral.
-
Unless already working in branch or instructed to branch - commit to default branch.
-
Work the person holds back stays on its own branch, never merged into the shared main until they release it: whatever stands on main may be published.
-
When committing a code change, first run the checks the repository defines for itself — its linter, its formatter in check mode, its type checker, its tests. Pure doc changes need none of them. Read them from where the project states them; never carry them here. A commit skill holding a project's commands is a second home for them, and it is wrong for every project but the one it was written in.
-
Commit when the work closes —
/verifyhas passed on it. Push as the project's local file states its way of working with git; a push is never implied by a commit.
<installed by="session">
S5 Commit the work of the current session only: another session's changes may be its work in
progress, and in doubt ask the person. Work on a unit this session took over is its own, the
holder's uncommitted changes to it included. Commit with the paths named, git commit -- <file>…,
each one this session wrote or moved, and stage nothing ahead of the commit; never a directory, a
glob, -A or a bare git commit — in a tree where other sessions run, the index is shared.
</installed>
<installed by="local">
L8 Prefix the subject with the loop step that produced the work, uppercase, then a colon — one of
these and no other: ALIGN, TICKET, PLAN, IMPLEMENT, VERIFY, MAINTAIN,
DISCOVER, RECALL, CONCLUDE; outside the ring, FIX for a repair taken on its own, EQUIP
for a change to the harness's own installation, DREAM for a record the second lobe wrote. A
name for what the commit touched — the entry file, the local rules, the question store, an RFC —
is not a step: a rule landed at an align is ALIGN, a question opened while planning is PLAN.
One prefix per commit; where the work spans two steps, take the dominant one and name the bleed in
the message.
</installed>
04 同仓库更多 Skills
verify
Use after an implementation pass, or to verify a landed slice before close. Whole verification of landed work: ticket, RFC, governing docs, and the project's verification set.
ticket
Use to decompose a parent work into independently-workable child tickets. Use to mint ticket(s), possibly a single one, when planning implementation without one.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
skill-up
Aid agent skill creation or modification. Use when creating a new skill or changing an existing one. Use whenever writing any agent instructions, whether to a file or directly in a reply.
setup-devops
Set up the project's engineering scaffolding, from toolchain to CICD and observability. Use when initializing a repo or filling a setup gap.
review-architecture
Explore the codebase for module-deepening opportunities — architectural improvements that raise testability and navigability. Use when asked to improve or refactor the architecture.