pr-draft

Create draft GitHub pull requests with Conventional Commits formatting.

3|1|Updated Aug 22, 2015
One-click install
npx skills add https://github.com/iimuz/dotfiles --skill pr-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-draft
Source: https://github.com/iimuz/dotfiles/tree/main/.config/copilot/skills/pr-draft
Command: npx skills add https://github.com/iimuz/dotfiles --skill pr-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

Standardizes draft PR creation by enforcing Conventional Commits formatting and validating inputs, reducing review friction and inconsistencies.

Core Features & Use Cases

  • Conventional Commit validation ensures PR types are correct and emojis are applied in titles.
  • Deterministic workflow uses only shipped scripts to review branch status and create PRs from the repo root.
  • Draft PR generation supports structured PR bodies with sections for related URLs, changes, confirmations, and review points, enabling consistent PR documentation.

Quick Start

From the repository root, run bash scripts/check-branch-status.sh and bash scripts/create-pr.sh to generate a draft PR.

Frequently Asked Questions about pr-draft

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

FAQPage Schema
How do I automate GitHub pull request creation with Conventional Commits formatting?

Automating GitHub pull request creation with Conventional Commits formatting is achieved by running bash scripts from the repository root to validate PR type, apply emoji-enhanced titles, and generate a structured draft PR body.

What is the best way to enforce consistent PR structure across multiple repository contributions?

The best way to enforce consistent PR structure is using deterministic scripts that validate inputs against a fixed PR type list and generate standardized draft PR bodies with sections for changes, related URLs, and review points.

Do I need the GitHub CLI installed to generate draft pull requests from the command line?

Yes, you need the GitHub CLI (gh) and git installed, as the workflow uses these dependencies to check branch status and create pull requests from your working directory.

Can I customize the PR type list when validating Conventional Commits for pull requests?

No, the PR type validation enforces a fixed list of Conventional Commits types, ensuring standardized formatting and reducing inconsistencies without allowing custom type definitions.

Why does my draft PR generation fail when running the create-pr script?

Draft PR generation fails if the working directory is not a git repository, or if the provided PR type does not pass validation against the fixed Conventional Commits list enforced by the script.

How does the check-branch-status script prepare my repository for pull request creation?

The check-branch-status script reviews the current repository state from the root directory to ensure the working environment is a valid git repository before proceeding to generate the draft pull request.