Use this skill to prepare a Topcoat pull request from the full branch diff. It guides you to write a Conventional Commits title and a concise body covering the change, verification performed, and an AI-use disclaimer when an agent creates the PR.
Always use this skill before opening a pull request in the Topcoat repository
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
A branch usually holds several commits: initial work, fixups, review responses, rebases. The title and body describe the net change landing on the base (usually main). Read the full diff first:
git diff <base>...HEAD
git log <base>..HEAD
Same Conventional Commits format as a commit message (see the commit skill). .github/workflows/semantic-pr.yml enforces that the type is one of feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert and that the subject is not capitalized. PRs are squash-merged, so the title becomes the landed commit and the release-plz changelog entry.
No template. Keep it short and high-signal:
check skill).Reviewers already know Topcoat and Rust. Include what they need to evaluate the change, and nothing else.
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.
Use this skill to check Topcoat changes locally before committing or opening a pull request. It runs the project’s Rust formatting, lint, test, and documentation commands, plus browser project checks when relevant, so problems can be caught before review.
Use this skill to write concise commit messages in the Topcoat project’s Conventional Commits format. It helps choose a change type and scope, describe the update clearly, and mark breaking changes so release notes and version bumps can be based on commit history.
Use this skill when building procedural macros for Topcoat in Rust. It explains how to preserve parsed syntax in AST nodes, separate parsing from meaning, and keep macro entry points focused on parsing input, expanding valid code, and reporting errors.
Use this skill to write long-form Markdown guides for Topcoat. It covers where documentation sources belong, how to structure explanations from basic to advanced, and how to keep prose plain, concise, and easier to maintain as implementations change.
Apply the project’s Rust conventions when editing code or documentation. The guidance covers module and type organization, workspace dependency declarations, plain English documentation, and tests that check meaningful behavior rather than fixed text.