菜单
Always use this skill before authoring a commit message in the Toasty repository
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | commit |
| description | Always use this skill before authoring a commit message in the Toasty repository |
Load this skill before writing any git commit message in this project.
Always read docs/dev/COMMITS.md before
authoring a commit message. It is the authoritative source for the
format, allowed types, scope conventions, subject/body/footer rules, and
breaking-change notation.
Maintainers reading the log already know Toasty and Rust. Keep the subject and body high-signal: state what changed and why. Skip restated context, obvious explanations, and throat-clearing. A maintainer should grasp the important bits in seconds.
Always use this skill before opening an issue in the Toasty repository
Always use this skill before authoring or editing a Toasty design document under docs/dev/design/
Always use this skill when running tests against dynamodb (DDB)
Always use this skill before opening a pull request in the Toasty repository
Author or edit any prose for the Toasty project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following project writing conventions
Bring the Toasty user guide and rustdoc back in sync with recent code changes by walking the git log for user-observable behavior and updating affected docs
