pull-request
Creates and opens pull requests from unmerged changes. Use when user asks to open a PR, create a pull request, make a PR, submit a PR, or handle unmerged/staged/unstaged changes that need a PR.
When & Why to Use This Skill
The Pull Request skill automates the transition from local development to collaborative code review by creating and opening pull requests directly from unmerged changes. It streamlines the DevOps workflow by enforcing best practices such as conventional commit formatting, automatic reviewer assignment based on git history, and linking relevant project management issues (GitHub/Jira), ensuring a standardized and efficient submission process.
Use Cases
- Automated Workflow Integration: Seamlessly convert staged or unstaged code changes into a formal pull request, reducing the manual overhead of switching between the terminal and browser.
- Standardized Commit Management: Ensure all pull request titles adhere to the 'conventional commits' format (e.g., feat, fix, chore), which facilitates automated changelog generation and cleaner version history.
- Enhanced Team Collaboration: Improve the quality of code reviews by automatically identifying and adding the most relevant reviewers based on file ownership and providing clear explanations of the 'why' behind specific code changes.
- Issue Tracking Synchronization: Automatically link pull requests to GitHub or Jira issues using 'Closes' or 'Related' tags to maintain a clear audit trail between tasks and code implementation.
| name | pull-request |
|---|---|
| description | Creates and opens pull requests from unmerged changes. Use when user asks to open a PR, create a pull request, make a PR, submit a PR, or handle unmerged/staged/unstaged changes that need a PR. |
Pull Requests
- MUST use the commit-message skill to craft git commit messages
- Title MUST follow conventional commits format:
type(scope): message - Title is used for squash merge commit
- SHOULD include
ClosesorRelatedreferencing GitHub or Jira issue if possible - SHOULD explain why, not just what changed
- SHOULD add reviewers based on git history of changed files
- SHOULD NOT include test plan