create-pr

Create GitHub pull requests with gh CLI and enforced title conventions.

2|Updated Aug 16, 2011
One-click install
npx skills add https://github.com/sakuro/dotfiles --skill create-pr-sakuro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/sakuro/dotfiles/tree/main/.config/claude/skills/create-pr
Command: npx skills add https://github.com/sakuro/dotfiles --skill create-pr-sakuro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-cli.

What problem does it solve?

This Skill simplifies creating GitHub Pull Requests by enforcing project conventions for titles, descriptions, and content. It ensures clarity and consistency for reviewers, reducing back-and-forth and accelerating the code review process.

Core Features & Use Cases

  • Convention-Driven Titles: Guides you in creating PR titles with required emoji codes and imperative mood, matching project standards.
  • Structured Descriptions: Enforces a clear PR body structure with essential sections like summary, changes, and test plan, making reviews more efficient.
  • Safe PR Creation: Utilizes the gh CLI with robust methods for handling complex Markdown content, preventing common formatting errors.
  • Use Case: A developer needs to open a pull request for a new feature but wants to ensure it meets all team standards for documentation and clarity. This skill guides them through creating a well-structured and compliant PR, from drafting the title to detailing the test plan.

Quick Start

Use the create-pr skill to open a pull request for my current branch, with the title :sparkles: Implement user profile page and a summary of the changes.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a GitHub pull request that follows my project's conventions?

Create a GitHub pull request using gh CLI with enforced conventions: structure your PR title with an emoji code and imperative mood, then populate the body with required sections like summary, changes, and test plan. This ensures consistency and speeds up code review.

What should a well-structured PR description include?

A well-structured PR description includes essential sections: a summary of the change, detailed list of changes made, test plan or verification steps, and any relevant context. This format helps reviewers understand scope and validate your work quickly.

Can I use gh CLI to automate pull request creation?

Yes, gh CLI supports automated PR creation with robust methods for handling Markdown content. You can pass PR titles and bodies via temporary files or heredoc syntax, preventing formatting errors and ensuring your description meets project standards.

How do I format a PR title correctly before submitting?

Format your PR title with a required emoji code followed by imperative mood language—for example, `:sparkles: Implement user profile page`. This convention makes PR history scannable and aligns with most team documentation standards.

What validation happens before a PR is created?

Before PR creation, the skill validates your branch readiness and commit history to ensure you're publishing from a valid state. It also enforces required and optional sections in your PR body structure to meet project requirements.

Does this work with multiple GitHub repositories?

Yes, this skill uses gh CLI to submit pull requests across any GitHub repository you have access to. The same title format and body structure apply regardless of which repo you're publishing changes to.

Related Skills