pr

Automate GitHub PR workflows from validation to squash merge.

Updated Mar 6, 2026

Search Tags:#automation #git #workflow #github #branching #merge #pull-request

Ready to run

npx skills add https://github.com/arre-ankit/skills --skill pr-arre-ankit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/arre-ankit/skills/tree/main/skills/pr
Command: npx skills add https://github.com/arre-ankit/skills --skill pr-arre-ankit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the PR workflow, reducing manual steps and human error in submitting changes.

Core Features & Use Cases

Structured PR lifecycle: validate builds, create branches, stage commits with conventional messages, push, and open PRs.
Deterministic merges: checkout main, rebase, and squash merge as part of standardizing releases.
Use Case: Ideal for teams submitting code changes via GitHub PRs and needing a repeatable, auditable process.

Quick Start

Run the PR workflow to submit your first change to a feature branch and open a PR against main.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I automate my GitHub pull request workflow from branch creation to merge?▼

Automating your GitHub pull request workflow handles validation, branch creation, commit staging with conventional messages, PR creation, and squash merges. This end-to-end process ensures repeatable, auditable code integration while reducing manual steps and human error in submitting changes.

What is the process for standardizing branch naming and commits in a GitHub PR lifecycle?▼

Standardizing branch naming and commits applies consistent conventions before pushing changes to GitHub. The PR lifecycle enforces structured validation, deterministic commit messages, and branch creation rules to maintain an auditable history for software projects using GitHub.

How do I perform a squash merge after rebasing main in my GitHub workflow?▼

To perform a squash merge after rebasing main, checkout the main branch, pull latest changes, rebase your feature branch against it, and execute the squash merge. This standardizes releases by combining feature commits into a single commit on main.

Can I use this PR automation workflow for team projects that require an auditable GitHub submission process?▼

Yes, you can use this PR automation workflow for team projects requiring an auditable GitHub submission process. It standardizes the pull request lifecycle for teams submitting code changes via GitHub PRs, providing a repeatable process from validation to deterministic merge.

Do I need any external dependencies or CI tools to automate PR creation and merging?▼

No external dependencies or CI tools are required to automate PR creation and merging. The workflow operates independently to validate builds, create branches, push commits, open PRs, checkout main, rebase, and squash merge without relying on additional components or external libraries.