draft-pr

Automate branch preparation, PR drafting, and pushing within a Git workflow.

51|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/g2i-ai/agents --skill draft-pr-g2i-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-pr
Source: https://github.com/g2i-ai/agents/tree/main/skills/draft-pr
Command: npx skills add https://github.com/g2i-ai/agents --skill draft-pr-g2i-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill eliminates guesswork in creating a feature branch, assembling a meaningful PR description, and pushing a draft PR, saving time and reducing errors.

Core Features & Use Cases

  • Create or verify a feature branch from the base branch.
  • Enforce a conventional commit message pattern for commits.
  • Generate a PR body via /pr-description and create a draft PR targeting the base branch.
  • Provide guidance for PR title including ticket keys when present.

Quick Start

Invoke the draft-pr workflow to prepare a clean branch, draft a PR body, and push a draft PR for review.

Frequently Asked Questions about draft-pr

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

FAQPage Schema
How do I automate creating a git branch and drafting a pull request?

Automating a git branch and draft pull request involves preparing a clean branch from a base branch, generating a PR body, and pushing a draft PR for review. This workflow enforces consistent PR practices and faster code integration.

What is a conventional commit message pattern and when do I need it for a pull request?

A conventional commit message pattern enforces a standardized format for git commits. You need it for a pull request to ensure consistent code review practices and maintain a clean, readable project history within your workflow.

How do I generate a PR body and title for a draft PR?

To generate a PR body and title for a draft PR, use a PR description generator to assemble the body, and include ticket keys in the title when present. This eliminates guesswork and reduces errors.

Can I integrate a PR description generator within my git workflow?

Yes, you can integrate a PR description generator within your git workflow to automate drafting a PR. It works by generating the PR body and creating a draft PR targeting the base branch for software teams.

What's the best way to enforce consistent PR practices for software teams?

The best way to enforce consistent PR practices is to automate branch creation, apply conventional commit messages, and generate standardized draft PRs. This eliminates guesswork and accelerates code integration.