pr

Automate pull request workflows from branch creation to merge.

Updated Feb 3, 2026

Search Tags:#git #workflow #branching #pr #code-review #pull-request

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR workflows are error-prone and require manual coordination across team members. This skill standardizes the end-to-end process from creating a feature branch to merging, reducing drift and improving review quality.

Core Features & Use Cases

Validates builds and checks before merging
Enforces branch naming conventions and commit discipline
Guides creation and handling of PRs, including squash merges and main rebases
Use case: Teams collaborating on a feature whose changes must go through formal review and automated checks.

Quick Start

Start a new feature by creating a branch, implement changes, and follow this workflow to validate, commit, push, and open a PR.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I standardize pull request workflows from branch creation to merge?▼

Standardize pull request workflows by automating branch creation, enforcing commit prefixes, and guiding squash merges. This ensures consistent code review and reduces drift across collaborative software projects.

What is the best way to enforce branch naming conventions and commit discipline?▼

Enforce branch naming conventions and commit discipline by applying standardized prefixes during the branching and committing steps. This maintains PR hygiene and consistency across team members.

How do I handle main rebases and squash merges in a collaborative git workflow?▼

Handle main rebases and squash merges through guided steps that validate builds before integration. This standardizes the end-to-end pull request process and reduces manual coordination errors.

Do I need automated build validation checks before opening a pull request?▼

Automated build validation checks are required before merging to ensure code stability. The workflow specifies validation steps and commands to run before pushing changes and creating a pull request.

Can I use this PR workflow for any collaborative software project?▼

Use this PR workflow for collaborative software projects requiring consistent code review and branching conventions. It applies to team environments where changes must go through formal review and automated checks.

Why does manual pull request coordination cause drift in team codebases?▼

Manual pull request coordination causes drift because it relies on inconsistent practices across team members. Standardizing the end-to-end process from feature branch to merge reduces errors and improves review quality.