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
npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a claude-codeWhat 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.mdwith 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-code2Manually: put the files in place
~/.claude/skills/pull-request-automation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pull-request-automation/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a codex2Manually: put the files in place
.agents/skills/pull-request-automation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a cursor2Manually: put the files in place
.cursor/skills/pull-request-automation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts skills/pull-request-automation2Manually: put the files in place
.github/skills/pull-request-automation/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/pull-request-automationManually: put the files in place
.devin/skills/pull-request-automation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill pull-request-automation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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