ops/pull-requests

Automates GitHub pull-request creation, review responses, merge decisions, and session-gated workflows via gh pr create.

3|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/deandum/claude-resources --skill ops-pull-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops/pull-requests
Source: https://github.com/deandum/claude-resources/tree/main/skills/ops/pull-requests
Command: npx skills add https://github.com/deandum/claude-resources --skill ops-pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides and automates pull-request creation, review responses, and merge decisions to enforce consistent collaboration patterns.

Core Features & Use Cases

  • Open PRs with gh pr create using repo templates
  • Respond to review comments with structured guidance
  • Choose and apply a merge strategy (squash, merge commit, rebase)
  • Mark PRs as ready or draft, and update descriptions after branch changes
  • Align PR activity with session gate rules (ops_enabled flag)

Quick Start

Ask the assistant to open a new PR for the current branch with a concise description and the preferred merge strategy.

Frequently Asked Questions about ops/pull-requests

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

FAQPage Schema
How do I automate pull request creation with GitHub templates?

You can automate pull request creation by using the gh pr create command, which enforces repository templates to standardize PR descriptions and formatting across team workflows.

What is the best way to choose a merge strategy for a pull request?

Choosing a merge strategy involves selecting squash, merge commit, or rebase based on your team's workflow needs, and the Skill applies the selected strategy automatically when finalizing the pull request.

How do I respond to GitHub code review comments with structured guidance?

Responding to code review comments is handled by providing structured guidance that aligns with team review flows, ensuring consistent and actionable responses to reviewer feedback on pull requests.

Can I update a pull request description after branch changes?

Updating a pull request description after branch changes is fully supported, allowing you to mark PRs as ready or draft and keep descriptions current as the branch evolves.

Does this pull request workflow require an ops_enabled session flag?

The pull request workflow respects an ops_enabled session flag, aligning PR activity with session gate rules to ensure merge decisions and updates only occur when the session is properly enabled.

What are the limitations of automating pull request merges across repositories?

Automating pull request merges is limited to GitHub repositories and depends on the ops_enabled flag, meaning activities outside GitHub or without the session flag active will not be processed.