open-pr

Name: open-pr
Availability: InStock
Author: AgentSystemLabs

Generate reviewer-ready GitHub pull requests from git diff metadata.

121|2|Updated Apr 24, 2026

Search Tags:#automation #testing #release management #pull request #github #git diff #code quality gates

Ready to run

npx skills add https://github.com/AgentSystemLabs/core --skill open-pr-agentsystemlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/open-pr
Command: npx skills add https://github.com/AgentSystemLabs/core --skill open-pr-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents premature or misleading pull requests by auto-synthesizing a reviewer-ready title and Summary/Test-plan from the full branch diff, then enforcing a pre-publish readiness gauntlet so the PR is truly shippable.

Core Features & Use Cases

Reviewer-ready PR synthesis: Generates an appropriate PR title and a structured body (Summary and Test plan) based on the complete set of changes since the base branch merge-base.
Mode-based readiness gates: Runs a residue sweep (fast), plus typecheck/lint (balanced), or a full production check-pr-readiness gauntlet (production) before publishing.
Safe publishing workflow: Requires mandatory confirmation, can return to the original base branch after publishing, pushes with upstream when needed, marks WIP commits as draft, and offers to branch out when invoked from the base branch.

Quick Start

Ask your agent to open a PR in production mode by running: open a PR for this branch.

Frequently Asked Questions about open-pr

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

FAQPage Schema

How do I automatically generate a GitHub pull request title and description from a branch diff?▼

You can generate a GitHub pull request by synthesizing a reviewer-ready title and structured Summary/Test-plan directly from the cumulative git diff against the base branch. This ensures consistent PR metadata across multi-commit branches without manual writing.

How do I enforce code quality gates before publishing a pull request?▼

To enforce code quality gates before publishing a pull request, you can apply mode-based readiness checks like a residue sweep, typecheck, lint, or a full production gauntlet. This prevents premature PRs by validating shippability before creation.

Does the PR generation workflow require manual confirmation before running gh pr create?▼

Yes, the PR generation workflow requires mandatory user confirmation before executing gh pr create. This safe publishing workflow ensures you review the synthesized PR metadata and readiness gate results before the pull request is published.

How do I handle upstream push and base-branch targeting when opening a pull request?▼

When opening a pull request, the workflow handles upstream push safely and targets the correct base from the repository default branch. If invoked from the base branch, it offers to branch out and can return to the original base after publishing.

What is the best way to manage WIP commits when creating a pull request?▼

The best way to manage WIP commits during pull request creation is to automatically mark them as draft. This integrates into the PR publishing workflow to indicate incomplete work while still synthesizing the diff metadata for review.

Can I run different levels of pre-publish readiness checks for feature delivery versus release workflows?▼

Yes, you can run different pre-publish readiness checks by mode for feature delivery, debugging, and release workflows. Modes range from a fast residue sweep to a balanced typecheck and lint, up to a full production check-pr-readiness gauntlet.