pr-management

Manage pull request lifecycle with templates, reviewer assignment, and merge criteria.

Updated Feb 3, 2026

Search Tags:#git #devops #code review #collaboration #pull request #github actions

Ready to run

npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill pr-management-dhruvinrsoni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-management
Source: https://github.com/dhruvinrsoni/agentskills-garden/tree/main/skills/80-collaboration/pr-management
Command: npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill pr-management-dhruvinrsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire pull request lifecycle, ensuring efficient code integration by managing templates, reviewer assignments, merge criteria, and stale PRs.

Core Features & Use Cases

Automated PR Templating: Standardizes PR submissions with pre-defined templates.
Intelligent Reviewer Assignment: Configures CODEOWNERS and assignment policies for efficient reviews.
Merge Criteria Enforcement: Ensures all checks and approvals are met before merging.
Stale PR Management: Automatically handles inactive PRs to keep the backlog clean.
Use Case: A development team can use this skill to automatically generate a PR template, assign reviewers based on code ownership, enforce that all CI checks pass, and automatically close PRs that have been inactive for over two weeks, significantly improving their code review velocity.

Quick Start

Configure PR management for the repository located at 'https://github.com/myorg/myrepo'.

Frequently Asked Questions about pr-management

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

FAQPage Schema

How do I automate pull request workflows for my development team?▼

Automating pull request workflows involves configuring PR templates, CODEOWNERS for reviewer assignment, branch protection rules for merge criteria, and stale bot settings for inactive PR handling. This streamlines code integration by standardizing submissions and enforcing review policies.

What is stale PR management and how does it keep the backlog clean?▼

Stale PR management automatically handles inactive pull requests, such as closing PRs inactive for over two weeks, to keep the backlog clean. Configuring stale bot settings identifies and resolves dormant code review requests.

How do I enforce merge criteria and code review approvals before integration?▼

Enforcing merge criteria requires configuring branch protection rules to ensure all CI checks pass and necessary approvals are met before merging. This Skill integrates with GitHub Actions to guarantee that code integration only happens when all review policies are satisfied.

Do I need CODEOWNERS and branch protection rules configured to manage pull requests?▼

Yes, configuring CODEOWNERS and branch protection rules is required. CODEOWNERS enables intelligent reviewer assignment based on code ownership, while branch protection rules enforce merge criteria for successful pull request management.

Can I standardize pull request submissions with pre-defined templates?▼

Yes, automated PR templating standardizes pull request submissions with pre-defined templates. This ensures all code integration requests follow a consistent format, allowing development teams to maintain efficient code review velocity.

What's the best way to assign reviewers based on code ownership in GitHub?▼

The best way to assign reviewers based on code ownership is by configuring a CODEOWNERS file. This enables intelligent, automated reviewer assignment for pull requests, ensuring appropriate team members review specific code changes.