Draft reviewer-ready pull request titles and descriptions from branch changes.
npx skills add https://github.com/sunsided/commit-skills --skill pr-sunsided
Please help me install this Agent Skill. Skill: pr Source: https://github.com/sunsided/commit-skills/tree/main/pr Command: npx skills add https://github.com/sunsided/commit-skills --skill pr-sunsided
Writing a pull request description that clearly explains what changed and why—without wasting the reviewer’s attention on commit-by-commit details.
Ask for: Draft the PR title and body for opening a pull request from the current branch, base it against main, and include review instructions.
High-intent search queries and answers about installing and using this skill.
To draft a pull request description without commit-by-commit details, generate a reviewer-oriented summary covering intent, motivation, and key load-bearing changes. This approach focuses on the overarching diff summarization rather than chronological commit history.
Automatic PR body formatting detects and follows the repository's pull_request_template.md headings when present. Template matching ensures the generated description respects existing sections without inventing new structural headings.
A reviewer-ready PR description should include a summary, motivation, key changes, risk notes, and actionable review instructions. Adding a 'where to start reading' section guides humans on what to inspect first during the code review.
Inferring issue links for PR closing automatically detects the likely issue reference from branch changes and formats it within the pull request body. This ensures the related issue is properly linked and closed upon merging.
Yes, you can generate a PR title and body that explicitly avoid tooling and test chatter. The output focuses solely on load-bearing changes and summary motivation, filtering out automated test logs and tooling noise.
The best way to provide review instructions in a pull request is to include a dedicated section detailing where to start reading and what to scrutinize. This actionable guidance helps reviewers navigate the diff summarization efficiently.
kage1020Analyze branch changes and generate a five-section Markdown diff report.
kirvinCreate a pull request for the current branch with an auto-generated title and body.
module-federationNormalize GitHub Pull Request titles to conventional commit format and rewrite bodies to match repository templates.
olioappsGenerate structured pull request descriptions from commits with testing and deployment notes.
