pr

Validate the full diff and checks, then open a pull request for the current branch.

64|8|Updated Oct 24, 2025

Search Tags:#automation #git #diff #ci-cd #code-review #pull-request

Ready to run

npx skills add https://github.com/GregorStocks/mage-bench --skill pr-gregorstocks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/GregorStocks/mage-bench/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/GregorStocks/mage-bench --skill pr-gregorstocks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers prepare and open a pull request for the current branch only after ensuring the full diff and checks pass, reducing manual PR errors and review friction.

Core Features & Use Cases

Diff validation: Compare the current branch against the baseline to surface changes that warrant a PR.
Pre-PR checks: Run linting, tests, and other checks locally before opening the PR.
Master integration: Merge in master to validate against the latest code and avoid CI headaches.
PR drafting & opening: Generate a PR title and body and create the PR on the repository.

Quick Start

Execute the PR workflow on the current branch to automatically validate changes and open a new pull request.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate opening a pull request after validating my git diff?▼

Automating a pull request after diff validation requires a workflow that compares the current branch against the baseline, runs local checks, merges master, and pushes the PR with a generated title and body. This ensures changes are reviewed locally before submission.

What is the best way to validate a code diff before creating a pull request?▼

Validating a code diff before a pull request involves comparing the branch against the baseline to surface changes, running linting and tests, and integrating master to catch conflicts. This pre-merge validation reduces CI headaches and manual review friction.

Can I merge master into my current branch before pushing a pull request?▼

Merging master into your current branch before pushing a pull request is a supported pre-PR step. It validates your changes against the latest code to avoid CI failures, ensuring the full diff and checks pass before the PR is opened.

Does this pull request workflow run linting and tests locally before submission?▼

Running linting and tests locally before submission is a core feature of this pull request workflow. These pre-PR checks validate the full diff and ensure the branch is stable before automatically generating a PR title and body for review.

How to generate a pull request title and body automatically from a branch diff?▼

Generating a pull request title and body automatically from a branch diff happens after pre-PR checks pass. The workflow analyzes the validated changes to draft a descriptive title and body, creating the PR on the repository for you.

When should I avoid automating pull request creation from a local branch?▼

Automating pull request creation from a local branch should be avoided when pre-merge checks or diff validation require manual intervention. If changes are not ready for local linting, tests, or master integration, the automated PR workflow may surface incomplete or failing edits.