skills.rest
alvarovillalbaa
alvarovillalbaaCOMMUNITY
Explore all skills by this author →
Website𝕏@alvarovillalbapGitHub

pr-management

Design pull request review, triage, and merge policies with landing gates.

Updated Feb 13, 2026
Search Tags:#code review#conflict resolution#triage#pull request management#CI gating#merge policy#engineering operations
One-click install
npx skills add https://github.com/alvarovillalbaa/plugins --skill pr-management-alvarovillalbaa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-management
Source: https://github.com/alvarovillalbaa/plugins/tree/main/engineering/skills/pr-management
Command: npx skills add https://github.com/alvarovillalbaa/plugins --skill pr-management-alvarovillalbaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PR workflows fail when review queues stall, merge risk rises, and teams can’t reliably decide what should be reviewed, escalated, or closed—especially at scale where small process gaps create big delays and quality regressions.

Core Features & Use Cases

  • Intent-first PR triage: close wrong-shaped work early and escalate judgment calls before wasting reviewer effort.
  • Multi-lens pre-merge review: apply focused review lenses (code quality, silent failures, test coverage, comment accuracy, type design) based on what the diff actually changes.
  • Merge-conflict lane + explicit landing gates: handle straightforward non-interactive conflicts and only declare readiness when concrete gates are satisfied.

Typical use: improve throughput and merge safety for a team managing large or long-lived PR queues (including 50–200+ engineer workflows), reducing latency without lowering quality.

Quick Start

Ask the AI to triage an active queue of pull requests using intent-first decisions and merge-ready landing gates.

Frequently Asked Questions about pr-management

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

FAQPage Schema
How do I reduce pull request latency and merge risk for a large engineering team?▼

Reduce pull request latency by applying intent-first PR triage to close wrong-shaped work early and explicit landing gates tied to CI outcomes. This limits merge risk by routing reviewer effort only to validated, merge-ready changes at team scale.

What is intent-first PR triage and how does it manage code review queues?▼

Intent-first PR triage classifies pull requests by their core intent before review, escalating judgment calls and closing incorrect work early. This manages code review queues by preventing wasted reviewer effort on unsuitable or premature contributions.

How do you handle merge conflicts in non-interactive pull request workflows?▼

Handle straightforward merge conflicts using a non-interactive conflict lane that resolves simple cases automatically. This pull request management method bypasses manual intervention, clearing the queue faster while escalating complex conflicts.

Can this PR management approach scale for 50 to 200+ engineer workflows?▼

Yes, this PR management approach scales for 50 to 200+ engineer workflows by implementing ordered validation paths for bugs versus features. Large teams use these explicit landing gates and operational metrics to maintain throughput without lowering quality.

What is multi-lens pre-merge review and when do I need it?▼

Multi-lens pre-merge review applies focused review lenses like code quality, silent failures, test coverage, and type design based on what the diff actually changes. You need it to ensure merge-commit readiness by catching specific defect types before integration.

Why do pull request queues stall and how can merge policy prevent it?▼

Pull request queues stall when teams cannot reliably decide what should be reviewed, escalated, or closed. A structured merge policy with intent-first classification and explicit landing gates prevents process gaps from creating big delays and quality regressions.

Related Skills

Explore More Software Engineering Skills→
0xHarbs0xHarbs
1

test

Detect test frameworks, scope tests to changed code, and report coverage.

Community
Advanced
OmniNode-aiOmniNode-ai
3

post-release-redeploy

Orchestrate post-merge redeployment with merge gate verification, package release, Docker rebuilds, and health checks.

Official
Advanced
AribSudiaAribSudia
2

arib-dev-review

Enforce an eight-gate code review process for pre-merge validation.

Community
Advanced
aviraldua93aviraldua93
2

pr-management

Manage pull request creation, review coordination, merging, and post-merge cleanup.

Community
Advanced