commit
Create a deliberate commit using the repo's canonical commit workflow and quality gates.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 4
01 前言 Front Matter
- name
- commit
- description
- Create a deliberate commit using the repo's canonical commit workflow and quality gates.
- classification
- passive
03 SKILL.md 正文
Commit
Use this skill when preparing a commit.
Read first
.agent/commands/commit.md.agent/directives/principles.md.agent/rules/no-verify-requires-fresh-authorisation.md
Checklist
- Check
git status. - Review
git diff --stagedand any related unstaged changes. - Ensure the relevant gates are green.
- Stage only the files the commit message truthfully describes.
- Prefer
uv run cz commit, or validate a manual message withuv run cz check. - Commit without bypassing hooks.
Local constraints
- This repo does not use aliases or compatibility layers for gate names.
- Prefer the canonical
uv run ...surfaces when you need to re-run checks. - Prefer
uv run cz ...for commit creation and validation. - If the change updates durable doctrine, include those docs in the same commit.
04 同仓库更多 Skills
tsdoc
Write code-adjacent API documentation and the matching durable doc updates.
systematic-debugging
Structured debugging workflow. Use when encountering bugs, test failures, or unexpected behaviour. Reproduce, isolate, hypothesise, verify, fix, regression test.
start-right-thorough
Thorough grounding — full directive read, metacognition, and execution outline.
start-right-quick
Quick grounding at session start — read directives, memory, and check practice box.
receiving-code-review
How to process code review feedback effectively. Understand before acting, verify suggestions technically, ask for clarification when needed. Complements the reviewer sub-agents.
napkin
Maintain a per-repo napkin file at .agent/memory/napkin.md that tracks mistakes, corrections, and what works. Always active, every session, unconditionally. Read distilled.md and napkin.md before doing anything. Write to the napkin continuously as you work. Log your own mistakes, not just user corrections.