pm-pr-workflow

Automate branch protection and PR-based workflows for main deployments.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-pr-workflow-bobmatnyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-pr-workflow
Source: https://github.com/bobmatnyc/claude-mpm-marketplace/tree/main/plugins/claude-mpm/skills/mpm-pr-workflow
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-pr-workflow-bobmatnyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch protection and PR workflows for main deployments, preventing direct pushes by non-privileged users.

Core Features & Use Cases

  • Branch protection enforcement before main operations
  • PR-based main-branch workflow with delegation to version-control
  • Clear user messaging and routing to appropriate workflows

Quick Start

Configure the plugin to enforce main-branch protection and route non-privileged users through feature-branch PR workflows.

Frequently Asked Questions about pm-pr-workflow

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

FAQPage Schema
How do I enforce branch protection and prevent direct pushes to the main branch?

Branch protection is enforced by automating PR-based workflows that check user permissions and route non-privileged users to feature branches before any main branch operations can proceed. This prevents uncontrolled direct pushes.

How do I automate pull request workflows for feature branch deployments?

Pull request workflows are automated by delegating PR creation to a version-control agent, which manages feature-branch PRs and checks git integration before allowing any changes to merge into the main branch.

Can I route non-privileged users to feature branches automatically?

Non-privileged users are automatically routed to feature branch workflows by checking their user permissions and directing them to create feature-branch PRs instead of allowing direct main-branch modifications.

What is a PR-based workflow for main-branch changes?

A PR-based workflow for main-branch changes is a controlled process where feature-branch PRs, user permission checks, and version-control delegation enforce safety before integrating code into the main branch.

Does this workflow support stacked or independent pull requests?

The workflow supports both stacked and independent PRs by routing them through feature branches and delegating their creation to a version-control agent for proper main-branch integration.

What are the limitations of automating main-branch protection with version control?

The automation requires integration with git checks and relies on delegating PR creation to a version-control agent, meaning workflow routing stops if these permission checks or version-control integrations are not properly configured.