git-pr

Automate pull request creation with project-specific templates and branch guidance.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/eleva-labs/agentic-coding-templates --skill git-pr-eleva-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/eleva-labs/agentic-coding-templates/tree/main/.claude/skills/shared/git-pr
Command: npx skills add https://github.com/eleva-labs/agentic-coding-templates --skill git-pr-eleva-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and accelerates pull request creation by aligning PRs with project conventions, reducing review time and confusion.

Core Features & Use Cases

  • PR type templates for Feature, Bug Fix, Hotfix, and Release PRs to ensure consistent titles and descriptions.
  • Branch guidance for naming and target bases to streamline workflows and reduce merge conflicts.
  • Automated metadata: Generates standardized PR body content, checks required reviewers, and seeds template fields to speed up reviews.
  • Use Case: A developer opens a feature branch and uses this skill to generate a ready-to-submit PR with the correct type and description.

Quick Start

  • Ensure you have the GitHub CLI installed.
  • Invoke the git-pr skill with the appropriate PR type and target base (e.g., feature from feature/xyz to development, or hotfix from hotfix/urgent to main).
  • Confirm or customize the generated PR details and submit.

Frequently Asked Questions about git-pr

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

FAQPage Schema
How do I create a pull request with a standardized template automatically?

To create a pull request with a standardized template, this Skill automates PR creation by applying project conventions for feature, bug fix, hotfix, and release workflows. It generates compliant titles, descriptions, and metadata prompts to streamline reviews.

What is the best way to enforce branch naming conventions for GitHub pull requests?

Enforcing branch naming conventions for GitHub pull requests is handled by providing branch guidance during PR creation. The Skill suggests appropriate branch names and target bases, reducing merge conflicts and aligning with your development workflow.

Can I generate different PR body templates for hotfixes versus regular feature branches?

Yes, you can generate different PR body templates for hotfixes versus feature branches. The Skill provides specific templates tailored for Feature, Bug Fix, Hotfix, and Release PRs to ensure consistent titles and descriptions across various development processes.

Do I need the GitHub CLI installed to automate pull request generation?

Yes, you need the GitHub CLI installed to automate pull request generation. The Skill relies on the GitHub CLI to invoke the workflow, apply the appropriate PR type templates, and submit the standardized PR details directly to your repository.

How does automated PR metadata speed up the code review process?

Automated PR metadata speeds up the code review process by generating standardized body content, checking required reviewers, and seeding template fields automatically. This ensures consistent PRs with minimal setup, reducing confusion and review time.