Pull Request Workflow
Guides the creation of detailed, standards-compliant pull requests from branch setup to final submission.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Structures PR bodies with a summary, bullet points, and inline markdown links to code.
- Validates staged changes and enforces proper branch naming conventions (`feature/`, `fix/`).
- Enforces specific formatting for PR titles (capitalized verbs, no prefixes) and bodies.
- Automates PR creation using `gh pr create` with self-assignment and reviewer suggestions.
- Analyzes the complete changeset against the base branch for a comprehensive PR description.
Use cases
- Standardizing the pull request process across a development team.
- Submitting a new feature or bug fix for code review.
- Creating detailed and easy-to-review PR descriptions with direct source code links.
FAQ
What does the Pull Request Workflow skill do?
This skill automates the creation of high-quality, standards-compliant GitHub pull requests. It guides you from validating staged changes and branch naming all the way to submitting a perfectly formatted PR.
What specific capabilities does it provide?
It validates branch names (e.g., `feature/`), analyzes the full changeset for a comprehensive description, formats PR titles and bodies with inline code links, and automates submission using `gh pr create` with self-assignment and reviewer suggestions.
How does this skill improve my workflow?
It saves significant time by automating tedious formatting and command-line tasks. By enforcing project standards for every submission, it improves consistency and accelerates the code review process for your entire team.
When should I use this skill?
Use this skill when you're ready to submit your code for review. You can activate it with prompts like "create a PR for this branch," "make a pull request," or by using the `/create-pr` command.