pr

Create draft pull requests with conventional titles and ticket links via GitHub CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a predictable, template-driven draft PR workflow by using the GitHub CLI, enforcing conventional commit titles and ticket links for traceability.

Core Features & Use Cases

  • Draft PR creation: creates a draft PR from the current feature branch using the repository's PR template and a conventional title format.
  • PR iteration workflow: supports the "pr iterate" cycle — rebase, lint, test, and push — to keep branches current and ready for review.
  • Guidance on usage constraints: avoids using this for reviewing others' PRs or fixing your own branch; use dedicated commands instead.
  • Use Case: when preparing a feature branch for review, automatically generate a consistent draft PR with a linked ticket.

Quick Start

Run the pr skill on a feature branch to create a draft PR with a conventional title and ticket link.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a draft pull request with a conventional commit title using the GitHub CLI?

To create a draft pull request with a conventional commit title, the skill uses the GitHub CLI to generate a draft PR from your current feature branch, automatically applying repository PR templates and extracting ticket links for traceability.

What is the PR iterate workflow for keeping a feature branch current?

The PR iterate workflow is a sequence of commands—rebase, lint, test, and push—that keeps your feature branch current with the main branch and ready for review, ensuring code quality before updating the draft pull request.

Do I need the gh CLI installed and authenticated to automate pull request creation?

Yes, you need the gh CLI installed and authenticated to automate pull request creation, as the skill relies on GitHub CLI commands to generate draft PRs, extract ticket IDs, and perform the iteration sequence.

Can I use this skill to review or fix other developers' pull requests?

No, you cannot use this skill to review or fix other developers' pull requests. The skill explicitly avoids reviewing others' PRs or fixing your own branches, recommending dedicated commands for those specific tasks instead.

How do I automatically link a ticket ID to a draft pull request?

To automatically link a ticket ID to a draft pull request, the skill extracts ticket IDs from your branch or commit context and embeds them into the standardized PR body generated from the repository's PR template.