pull-requests

Enforce pull request governance for titles, reviews, and merge practices.

2.0k|126|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/coder/mux --skill pull-requests-coder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-requests
Source: https://github.com/coder/mux/tree/main/.mux/skills/pull-requests
Command: npx skills add https://github.com/coder/mux --skill pull-requests-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for creating and managing Pull Requests in this repository to improve collaboration, consistency, and release quality.

Core Features & Use Cases

  • Lifecycle Rules: enforce branch naming, squash merges, and correct base branches to minimize disruption.
  • CI & Validation: align checks, reviews, and merging criteria to ensure code quality before integration.
  • Status Decoding: provide clear merge readiness indicators and guidance for conflict resolution.

Quick Start

Follow these guidelines when submitting a PR to ensure clean reviews and predictable merges.

Frequently Asked Questions about pull-requests

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

FAQPage Schema
How do I enforce consistent pull request guidelines for my development workflow?

Pull request governance improves collaboration by defining lifecycle rules for branch naming, squash merges, and correct base branches to minimize disruption during integration.

What is the best way to align CI checks and code reviews before merging?

Aligning CI checks and code reviews involves applying validation criteria to ensure code quality before integration, providing clear merge readiness indicators and guidance for conflict resolution.

How do I manage pull request lifecycle rules to minimize branch disruption?

Managing pull request lifecycle rules requires enforcing branch naming conventions, squash merges, and targeting correct base branches to minimize disruption and ensure predictable merges.

Can I use this PR governance workflow for projects with multiple reviewers and CI checks?

PR governance workflows apply to software development environments where multiple reviewers and CI checks require consistent PR standards to maintain collaboration and release quality.

How do I decode merge readiness status and resolve pull request conflicts?

Decoding merge readiness status provides clear indicators for integration readiness and actionable guidance for resolving conflicts, ensuring code quality checks are met before merging.