Skip to main content
skill CX Codex

pull-request-automation — Claude Code skill

pull-request-automation — a skill for Claude, Cursor and Codex that adds a PR template, checklists, reviewer assignment and auto-merge rules. Handy when everyone on the team reviews by their own habits.

MIT 1 installs ★ 386 updated 2026-03-04

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a claude-code
Open on GitHub

What pull-request-automation does

This skill puts the tedious parts of a pull request on rails: a description template with boxes for change type and testing, rules for picking reviewers, and conditions for merging on its own. Smaller guides cover PR title and commit message validation, plus a floor for code coverage.

Everything hangs off one SKILL.md with a starter template for .github/pull_request_template.md. The working implementations sit in references/ — GitHub Actions workflows for review assignment and merge on approval, a GitLab setup, Bors with conventional commit checks.

Configs exist for GitHub Actions, GitLab and Bors; any other CI means porting the logic yourself. Auto-merge also needs checks that actually run: merging on a red pipeline is listed among the mistakes to avoid.

What it helps with

  • standardise the PR description across a team
  • assign reviewers from code ownership automatically
  • switch on auto-merge after approval and green CI
  • reject PR titles and commits that break the convention
  • set a minimum code coverage gate

Example prompts for the agent

  • Set up auto-merge on GitHub Actions: merge after approval once every check passes.
  • Write a .github/pull_request_template.md with boxes for change type and testing.
  • Add a workflow that validates PR titles against conventional commit.

How to install pull-request-automation

1Skills CLI (Vercel)

npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a claude-code

2Manually: put the files in place

~/.claude/skills/pull-request-automation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pull-request-automation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about pull-request-automation

How do I install pull-request-automation in Claude Code?

Run npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a claude-code. The skill lands at ~/.claude/skills/pull-request-automation/SKILL.md.

What does pull-request-automation do?

It gives you a PR template with checklists, rules for reviewer assignment, and auto-merge conditions. Reference guides add PR title validation, commit message checks and a coverage requirement.

Which CI systems does it cover?

It ships reference configs for GitHub Actions, GitLab and Bors. On any other CI you adapt the logic yourself.

Source text

SKILL.md · MIT
---
name: pull-request-automation
description: >
  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](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)

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

| Guide | Contents |
|---|---|
| [GitHub Actions: Auto Review Assignment](references/github-actions-auto-review-assignment.md) | GitHub Actions: Auto Review Assignment |
| [GitHub Actions: Auto Merge on Approval](references/github-actions-auto-merge-on-approval.md) | GitHub Actions: Auto Merge on Approval |
| [GitLab Merge Request Automation](references/gitlab-merge-request-automation.md) | GitLab Merge Request Automation |
| [Bors: Merge Automation Configuration](references/bors-merge-automation-configuration.md) | Bors: Merge Automation Configuration, Conventional Commit Validation |
| [PR Title Validation Workflow](references/pr-title-validation-workflow.md) | PR Title Validation Workflow |
| [Code Coverage Requirement](references/code-coverage-requirement.md) | 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

© aj-geddes · MIT · aj-geddes/useful-ai-prompts

Similar skills

All skills for Code review and refactoring →

From the same set151

The whole set →
api-response-optimization api-response-optimization — a coding-agent skill that trims payloads, adds caching and compression, and gives you a checklist for slow API endpoints. CX Codex +1 491installs accessibility-compliance The accessibility-compliance skill guides accessibility work for WCAG 2.1/2.2, keyboard navigation, screen readers and a11y checks in web interfaces. CX Codex +1 490installs background-job-processing A skill for wiring up background job processing: task queues, workers, scheduling and retries. Useful when emails, reports or large exports should not block the request path. CX Codex +1 490installs git-workflow-strategy git-workflow-strategy — a skill that helps your agent pick a branching model and walk a feature, release or hotfix through the right steps. Useful when the team has no shared branch rules. CX Codex +1 489installs incident-response-plan The incident-response-plan Claude Code skill helps build procedures for security incidents. It applies to breach handling, response playbooks, and forensic investigations. CX Codex +1 488installs zero-trust-architecture zero-trust-architecture guides AI coding agents to implement Zero Trust security with identity verification and microsegmentation. Useful for cloud-native apps. CX Codex +1 488installs frontend-state-management Guides your agent through frontend state management: Redux, MobX, Zustand or the Context API. CX Codex +1 487installs cross-platform-compatibility cross-platform-compatibility guides the agent to handle OS differences without breaking builds. It enforces safe path resolution, line endings, and dependency handling on Windows, macOS, and Linux. CX Codex +1 485installs

Project sponsors

Companies that keep this analytics open