메뉴
Always use this skill before authoring a commit message in the Toasty repository
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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
| 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.
