Prepare a Toasty pull request by reviewing the full change against its base branch and drafting a concise title and body from the net diff. It also covers the required template, rendered links for major Markdown changes, and label handling.
Always use this skill before opening a pull request in the Toasty repository
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Prepare concise Git commit messages for the Toasty project by first checking its authoritative commit guide. The skill focuses on describing what changed and why, using the project's required format, types, scopes, and breaking-change notation.
Prepare Toasty design documents under `docs/dev/design/` using the required template, audience, and concise writing conventions. The skill guides document structure and illustrative Rust examples, and outlines the proposal and roadmap steps for non-trivial features.
Write clear Toasty issues by choosing the right template for a bug report or feature proposal and filling in its required fields. It helps describe observed behavior, reproduction steps, proposed APIs, and alternatives in concise, factual language.
Write or edit Toasty documentation, design notes, READMEs, pull request descriptions, issues, and commit bodies using the project's prose conventions. It favors direct, factual language, concrete examples, active voice, and descriptions of current behavior.