Menu
Always use this skill before opening a pull request in the Toasty repository
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Always use this skill before opening an issue in the Toasty repository
Always use this skill before authoring a commit message 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)
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 | pr |
| description | Always use this skill before opening a pull request in the Toasty repository |
Load this skill before opening a pull request in this project.
A branch usually contains several commits — initial work, fixups, review responses, rebases. The PR title and body describe the net change that will land on the base branch, not the most recent commit.
Identify the PR's base branch first. It is usually main, but a PR
stacked on another feature branch has that feature branch as its base.
Then read the full diff against the base:
git diff <base>...HEAD
git log <base>..HEAD
Draft the title and body from what that diff actually contains.
Follows the same Conventional Commits format as a commit message — it
becomes the squash-merge commit. See
docs/dev/COMMITS.md.
Fill in the template at
.github/pull_request_template.md.
Keep the section headings and the checklist; replace the HTML comment
placeholders with real content. Delete checklist items that do not
apply rather than leaving them unchecked with no explanation.
When a PR's primary change is adding or substantially modifying a single
markdown file (e.g., a design doc or a major docs rewrite), put a link
to the rendered version on the branch as the first line under
## Summary:
## Summary
[Rendered](https://github.com/tokio-rs/toasty/blob/<branch-name>/<path-to-file>.md)
<rest of summary>
Use the PR's head branch name in the URL so the link renders the
version under review, not what's on main. PR
#787 is an example.
Reviewers already know Toasty and Rust. Keep the body high-signal: state the problem, the change, and anything a reviewer needs to know to evaluate it. Skip restated context, obvious explanations, and throat-clearing. A reviewer should grasp the important bits in seconds.
Do not apply labels when creating the PR. Maintainers triage and label
PRs separately — see docs/dev/labels.md.
Passing --label to gh pr create bypasses that process.