Skip to content

tokio-rs/topcoat / .agents/skills/pr

Always use this skill before opening a pull request in the Topcoat repository

Opening Pull Requests

Describe the diff, not the latest commit

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

Title

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.

Body

No template. Keep it short and high-signal:

  • Summary -- what the change does and why, drawn from the diff.
  • Testing -- how you verified it (which checks you ran; see the check skill).
  • Disclaimer -- if you are an AI agent creating the PR, add a disclaimer about specific model and how AI was used to create the change.

Reviewers already know Topcoat and Rust. Include what they need to evaluate the change, and nothing else.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall