pr-manager

Automates PR lifecycle with FABER metadata across supported SCM platforms.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill pr-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-manager
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/repo/skills/pr-manager
Command: npx skills add https://github.com/fractary/claude-plugins --skill pr-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Manages pull requests throughout their lifecycle, including creation, commenting, reviewing, merging, and linking to FABER context.

Core Features & Use Cases

  • Create and review PRs with FABER metadata
  • Link work item and spec to PR
  • Enforce merge safety and CI checks
  • Post-merge cleanup and status updates

Quick Start

Create a PR for the Build/Release outputs and attach FABER context.

Frequently Asked Questions about pr-manager

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

FAQPage Schema
How do I automate pull request creation and merging with work item linking?

Pull request automation manages the full lifecycle—creation, commenting, reviewing, approving, and merging—while embedding FABER metadata and linking work items to PRs. This enforces merge safety checks, validates CI status, and applies your configured merge strategy across supported source control platforms.

Can I enforce merge safety and CI validation before merging pull requests?

Yes. The Skill enforces protected-branch safety checks and CI status validation before merges, ensuring only passing builds and compliant PR metadata merge. It integrates with platform-specific source-control handlers to block unsafe merges automatically.

What does PR body template enforcement and FABER metadata embedding do?

PR body templates standardize pull request structure and content. FABER metadata embedding attaches context—specs, work items, and lifecycle state—directly into PR bodies, making PR intent and dependencies visible to reviewers and downstream tooling.

How do I handle post-merge cleanup and status updates after merging?

The Skill automates post-merge cleanup and status updates, handling branch deletion, work item status transitions, and notification dispatch. This closes the PR lifecycle loop and keeps downstream systems in sync with merge completion.

Does this work with multiple source control platforms?

Yes. The Skill integrates with platform-specific source-control handlers, supporting programmatic and user-initiated PR operations across multiple SCM platforms with consistent merge strategies and FABER metadata handling.

What are the prerequisites for setting up PR lifecycle automation?

You need bash and jq as runtime dependencies. The Skill expects configured work item linking patterns, merge strategy preferences, and access to your source-control platform's API or credentials for PR operations and CI status checks.