mcpField
P
pull-request-automation

pull-request-automation

github.com/aj-geddesTesting & quality373465 installsUpdated 34w ago
Repository

About pull-request-automation

A skill for designing pull request workflows that standardize reviews, enforce quality checks, and reduce manual steps. It covers templates, reviewer assignment, validation, and merge automation.

Key features

  1. 01PR templates for consistent submissions
  2. 02Automated reviewer assignment
  3. 03Approval-based merge automation
  4. 04Title and commit validation
  5. 05Coverage and CI checks

Use cases

  1. 01Standardizing code review requests
  2. 02Assigning reviewers by code ownership
  3. 03Blocking merges when checks fail
  4. 04Organizing PRs with labels

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill pull-request-automation

After installing, type/pull-request-automationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
bors-merge-automation-configuration.md
code-coverage-requirement.md
github-actions-auto-merge-on-approval.md
github-actions-auto-review-assignment.md
gitlab-merge-request-automation.md
pr-title-validation-workflow.md
scripts/
scaffold-tests.sh
templates/
test-template.js

Details

From the project README

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

Comments

Markdown supported