Opening Pull Requests
SkillDev toolsGuides your agent to follow the repository's rules when opening a pull request in Topcoat.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Opening Pull Requests skill
About this capability
Always use this skill before opening a pull request in the Topcoat repository
What this skill tells your AI
The instructions your AI receives, as published by tokio-rs/topcoat in .agents/skills/pr/SKILL.md and read by ahel’s review.
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
checkskill). - 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.
Signals
- GitHub stars
- 5k
- Forks
- 175
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
pr-6- Source
- github.com/tokio-rs/topcoat