pr

Route pull request creation through a dedicated skill with the --web flag.

8|1|Updated Jul 16, 2013
One-click install
npx skills add https://github.com/844196/dotfiles --skill pr-844196
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/844196/dotfiles/tree/main/files/dot_claude/exact_local-marketplace/exact_github/exact_skills/exact_pr
Command: npx skills add https://github.com/844196/dotfiles --skill pr-844196

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes and standardizes the process of creating pull requests, ensuring consistency and adherence to browser-based review flows instead of direct command-line PR creation.

Core Features & Use Cases

  • Guided PR creation: routes PR requests through a dedicated skill to prepare consistent titles and descriptions.
  • Browser-based finalization: opens the PR page in the browser for final user review and merging.
  • Workflow compliance: enforces the required --web flow and proper branch handling before PR submission.

Quick Start

Tell the agent to create a PR using this skill and then review and finalize it in the browser.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I standardize git pull request creation for browser-based review?

Standardize pull request creation by routing PR requests through a dedicated skill that prepares consistent titles and descriptions, then opens the PR in a browser for final user review and merging.

Why does this PR workflow require opening the browser instead of direct command-line creation?

Opening the PR in the browser ensures safety and visibility by enforcing a web-based review flow, preventing direct command-line PR creation and allowing final user review before merging.

How do I create a pull request using a guided workflow with proper branch handling?

Create a pull request by telling the agent to draft the branch and messages, which routes the request through the PR skill to handle branch preparation and open the PR page in the browser.

Can I use gh pr create directly with this pull request skill?

No, this skill avoids invoking gh pr create directly, instead routing the request through a dedicated PR skill that enforces the required web flow and proper branch handling for PR submission.

What's the best way to ensure workflow compliance when submitting a git branch pull request?

Ensure workflow compliance by using a dedicated PR skill that enforces the required web flow and proper branch handling before PR submission, opening the page in the browser for final user review.

When should I not use direct command-line PR creation in my git workflow?

Avoid direct command-line PR creation when you need standardized titles and descriptions with browser-based finalization, using a dedicated skill instead to ensure safety and visibility during merge review.