pr-handler

Automate the five-phase PR gatekeeping workflow for Draft PRs.

12|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/blackplume233/Actant --skill pr-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-handler
Source: https://github.com/blackplume233/Actant/tree/main/.agents/skills/pr-handler
Command: npx skills add https://github.com/blackplume233/Actant --skill pr-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires issue-manager.

What problem does it solve?

PR Gatekeeper SubAgent automates the validation, merge, and delivery pipeline for Draft PRs created by the Multi-Agent Pipeline, reducing manual review toil and preventing unsafe merges.

Core Features & Use Cases

  • Orchestrates a five-phase PR flow (Discovery, Validation Gate, Local Merge, Update Spec, Ship) triggered by mentions like "/handle-pr" or "review pr".
  • Enforces safety rules (no force push, no secret files, no bypassing hooks) and syncs corresponding Issues during Ship.
  • Supports integration with Issue Manager skill to synchronize related issues automatically.
  • Use Case: when a Draft PR is opened, this skill validates, merges locally, updates specs, and closes the PR with issue synchronization.

Quick Start

Invoke the pr-handler skill with a PR number or URL to start the PR handling workflow.

Frequently Asked Questions about pr-handler

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

FAQPage Schema
How do I automate GitHub pull request validation and merging for draft PRs?

Automating GitHub pull request validation and merging for draft PRs involves a phase-based workflow: Discovery, Validation Gate, Local Merge, Update Spec, and Ship. This process reduces manual code review toil by enforcing safety rules and synchronizing issues automatically.

What is the best way to prevent unsafe merges in an automated code review pipeline?

Preventing unsafe merges in an automated code review pipeline requires enforcing strict safety rules, such as blocking force pushes, preventing secret file modifications, and ensuring no bypassing of Git hooks. This ensures secure PR gatekeeping before shipping.

How do I synchronize related GitHub issues automatically when a pull request is merged?

Synchronizing related GitHub issues automatically when a pull request is merged is handled during the Ship phase. It coordinates with an Issue Manager dependency to close corresponding issues and update specs across the repository.

Can I use a multi-agent pipeline to handle code review and spec updates for GitHub PRs?

Yes, you can use a multi-agent pipeline to handle code review and spec updates for GitHub PRs. The workflow validates draft PRs, merges them locally, updates specifications, and closes the PR while synchronizing related issues.

Do I need an issue manager dependency to automate PR gatekeeping workflows?

Yes, an issue manager dependency is required to automate PR gatekeeping workflows effectively. It coordinates related issues during the Ship phase, ensuring that issue synchronization happens automatically when the pull request is closed.

What are the limitations of automating pull request workflows with phase-based processing?

Limitations of automating pull request workflows with phase-based processing include strict adherence to the five phases (Discovery, Validation, Local Merge, Spec Update, Ship) and a hard dependency on the Issue Manager for issue synchronization, which must both be present.