openmates:pullrequest

To create a pull request from dev to main, this Skill fetches remote refs, categorizes commit history into features and bug fixes, and generates a developer-ready PR description via gh. It ensures consistent formatting for routine branch-to-branch PR creation.

Commits are categorized for a GitHub PR description by analyzing full commit messages for semantic grouping. This Skill organizes commit history into features, bug fixes, improvements, and other maintenance so the PR description is readable.

You can prepare a draft release after merging a dev to main pull request using this Skill's optional post-merge draft release workflow. It creates the PR targeting main from dev, then guides you through preparing the subsequent release draft.

The best way to summarize branch differences before opening a PR is using remote refs to compute commit counts. This Skill validates differences between origin/main and origin/dev, showing commits on dev not in main for an accurate PR summary.

This PR creation workflow requires the GitHub CLI (gh) to create the pull request using base main and head dev. It relies on gh to execute the final PR creation step after analyzing and categorizing the commit history.

Your pull request descriptions lack consistent formatting due to vague commit summarization. This Skill solves that by automatically organizing commit history into structured categories, avoiding inconsistent formatting and generating clear developer-ready PR descriptions.