Pull Request Automation
Automate pull request workflows with templates, checklists, auto-merge rules, and review assignme…
by aj-geddes · MIT
The skill
Automate pull request workflows with templates, checklists, auto-merge rules, and review assignments. Reduce manual overhead and improve consistency.
Pull Request Automation
Table of Contents
Overview
Implement pull request automation to streamline code review processes, enforce quality standards, and reduce manual overhead through templated workflows and intelligent assignment rules.
When to Use
- Code review standardization
- Quality gate enforcement
- Contributor guidance
- Review assignment automation
- Merge automation
- PR labeling and organization
Quick Start
Minimal working example:
# .github/pull_request_template.md
## Description
Briefly describe the changes made in this PR.
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Documentation update
## Related Issues
Closes #(issue number)
## Changes Made
- Change 1
- Change 2
## Testing
- [ ] Unit tests added/updated
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| GitHub Actions: Auto Review Assignment | GitHub Actions: Auto Review Assignment |
| GitHub Actions: Auto Merge on Approval | GitHub Actions: Auto Merge on Approval |
| GitLab Merge Request Automation | GitLab Merge Request Automation |
| Bors: Merge Automation Configuration | Bors: Merge Automation Configuration, Conventional Commit Validation |
| PR Title Validation Workflow | PR Title Validation Workflow |
| Code Coverage Requirement | Code Coverage Requirement |
Best Practices
✅ DO
- Use PR templates for consistency
- Require code reviews before merge
- Enforce CI/CD checks pass
- Auto-assign reviewers based on code ownership
- Label PRs for organization
- Validate commit messages
- Use squash commits for cleaner history
- Set minimum coverage requirements
- Provide detailed PR descriptions
❌ DON'T
- Approve without reviewing code
- Merge failing CI checks
- Use vague PR titles
- Skip automated checks
- Merge to protected branches without review
- Ignore code coverage drops
- Force push to shared branches
- Merge directly without PR
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: aj-geddes/pull-request-automation-31721606058.
Details
- Publisher
- aj-geddes
- Category
- Software Development › Source control & code review
- License
- MIT
- Updated
- 2026-03-04
References
More from aj-geddes
- A/B Test Analysis Design and analyze A/B tests, calculate statistical significance, and determine sample sizes for…
- Access Control Rbac Implement Role-Based Access Control (RBAC), permissions management, and authorization policies.
- Accessibility Compliance Implement WCAG 2.1/2.2 accessibility standards, screen reader compatibility, keyboard navigation,…
- Accessibility Testing Test web applications for WCAG compliance and ensure usability for users with disabilities.