Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Pull Request Automation

  • 413 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

pull-request-automation is a Claude Code skill that automates pull request templates, reviewer assignment, labels, merge rules, and CI gates so developers who ship through GitHub or GitLab can keep review hygiene consist

About

pull-request-automation is a Claude Code skill from aj-geddes/useful-ai-prompts that helps developers wire consistent pull request workflows across GitHub and GitLab. It scaffolds PR templates with change-type checklists, links issues, and documents testing expectations, then points to six reference guides for auto review assignment, auto-merge on approval, GitLab merge request automation, Bors merge queues, PR title validation, and code-coverage requirements. The skill encodes best practices such as requiring reviews before merge, enforcing passing CI, auto-labeling PRs, validating conventional commits, and blocking coverage drops. Developers reach for pull-request-automation when review assignment is ad hoc, PR descriptions vary wildly, or merge rules need codifying in GitHub Actions or GitLab CI instead of tribal knowledge.

  • Generates structured PR titles and descriptions from branch diffs
  • Suggests reviewers, labels, and linked issues automatically
  • Enforces review checklists and merge readiness criteria
  • Integrates with CI status and conventional commit conventions

Pull Request Automation by the numbers

  • 413 all-time installs (skills.sh)
  • Ranked #115 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill pull-request-automation

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs413
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you automate PR reviews and merge checks?

Automate pull request creation, descriptions, labels, reviewers, and merge checks so teams ship code faster with consistent review hygiene.

Who is it for?

Developers maintaining GitHub or GitLab repos who want templated PRs, automated reviewer routing, and enforced merge gates without writing every workflow from scratch.

Skip if: Solo repos with no review process, or teams already standardized on a fully custom internal platform unrelated to GitHub/GitLab pull requests.

When should I use this skill?

A developer asks to automate PR creation, descriptions, labels, reviewers, merge checks, or GitHub Actions/GitLab CI review workflows.

What you get

PR templates, GitHub Actions or GitLab CI workflows, reviewer assignment rules, merge automation config, and title or coverage validation jobs.

  • pull_request_template.md
  • Review assignment workflows
  • Merge and validation CI jobs

By the numbers

  • Includes six reference guides for review assignment, merge automation, and validation
  • Documents PR template sections for change type, issues, changes, and testing

Files

SKILL.mdMarkdownGitHub ↗

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:

GuideContents
GitHub Actions: Auto Review AssignmentGitHub Actions: Auto Review Assignment
GitHub Actions: Auto Merge on ApprovalGitHub Actions: Auto Merge on Approval
GitLab Merge Request AutomationGitLab Merge Request Automation
Bors: Merge Automation ConfigurationBors: Merge Automation Configuration, Conventional Commit Validation
PR Title Validation WorkflowPR Title Validation Workflow
Code Coverage RequirementCode 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

Related skills

How it compares

Use pull-request-automation for repo-native PR workflow scaffolding; use a generic CI skill when you only need unrelated pipeline stages.

FAQ

Which platforms does pull-request-automation cover?

pull-request-automation covers GitHub pull requests and GitLab merge requests. Reference guides include GitHub Actions for review assignment and auto-merge, GitLab MR automation, and Bors merge-queue configuration for batched merges.

What files does pull-request-automation generate?

pull-request-automation starts with .github/pull_request_template.md and points to workflow files for reviewer assignment, title validation, coverage checks, and merge automation. Teams adapt the scaffolds to their branch protection and CI rules.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.