Pull Request Automation

aj-geddes/useful-ai-prompts/skills/pull-request-automation

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Automate pull request workflows with templates, checklists, auto-merge rules, and review assignments. Reduce manual overhead and improve consistency.

AI-generated overview

Automates pull request workflows with templates, review assignment, auto-merge rules, and CI checks.

What it does
This skill provides guidance and configuration examples for automating pull request and merge request workflows. It covers PR templates, auto review assignment, auto-merge on approval, Bors merge automation, PR title validation, and code coverage requirements. It also ships a test scaffolding script and a test template, and includes reference guides for GitHub Actions and GitLab.
When to use it
Use it when standardizing code review, enforcing quality gates, automating reviewer assignment, or setting up merge automation in a repository. It suits teams wanting consistent PR practices across GitHub or GitLab.
Requirements
Requires a Git repository hosted on GitHub or GitLab and CI/CD configuration (GitHub Actions or GitLab CI). Ships executable scripts (scripts/scaffold-tests.sh) and a test template (templates/test-template.js).

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:

markdown
# .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:

GuideContents
GitHub Actions: Auto Review Assignment [blocked]GitHub Actions: Auto Review Assignment
GitHub Actions: Auto Merge on Approval [blocked]GitHub Actions: Auto Merge on Approval
GitLab Merge Request Automation [blocked]GitLab Merge Request Automation
Bors: Merge Automation Configuration [blocked]Bors: Merge Automation Configuration, Conventional Commit Validation
PR Title Validation Workflow [blocked]PR Title Validation Workflow
Code Coverage Requirement [blocked]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

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/pull-request-automationat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal