skills.rest
khoi
khoiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github-create-pr

Create GitHub pull requests with labels, templates, and standardized titles.

16|2|Updated Mar 29, 2018
Search Tags:#automation#github#pr#code-review#labels#pull-request
One-click install
npx skills add https://github.com/khoi/dotfiles --skill github-create-pr-khoi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-create-pr
Source: https://github.com/khoi/dotfiles/tree/main/chezmoi/dot_agents/skills/github-create-pr
Command: npx skills add https://github.com/khoi/dotfiles --skill github-create-pr-khoi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a well-structured GitHub pull request with proper labels, branch naming, and description formatting. Use when changes are ready to be submitted as a PR.

Core Features & Use Cases

  • Enforces waiting for user approval before creating the PR.
  • Shows complete PR content in chat before submission.
  • Applies project-wide PR conventions for labeling, titling, and description formatting.

Quick Start

Describe the changes you want to include and let the skill draft a properly labeled, formatted PR ready for review.

Frequently Asked Questions about github-create-pr

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

FAQPage Schema
How do I create a well-structured GitHub pull request with proper labels?▼

To create a well-structured GitHub pull request, draft your changes and let the automation format the description, apply project-wide labeling conventions, and standardize the title and branch naming for immediate review.

Can I review the pull request content before it gets submitted to GitHub?▼

Yes, you can review the pull request content before submission. The system enforces waiting for your explicit approval and displays the complete PR content directly in the chat before creating it on GitHub.

What is the best way to enforce PR conventions for titling and branch naming?▼

The best way to enforce PR conventions is using an automated tool that applies project-wide standards for titling, branch naming, and description formatting automatically when changes are ready for pull request submission.

Do I need to manually format my pull request description when using automation?▼

No, you do not need to manually format your pull request description. The automation takes your described changes and applies standardized formatting, templates, and labels to build a polished PR.

When should I use an automated tool for GitHub PR creation?▼

You should use an automated tool for GitHub PR creation in software development scenarios where your code changes are fully ready for submission and require proper labeling, standardized titles, and structured descriptions.

Related Skills

Explore More Software Engineering Skills→
LaiTszKinLaiTszKin
4

open-source-pr-workflow

Prepare review-ready pull requests with standardized branch naming and structured English PR bodies.

Community
Advanced
ybbms777ybbms777
1

resolve-pr-feedback

Process GitHub pull request review feedback end-to-end with gh and jq.

Community
Advanced
rafaelportugalrafaelportugal
2

PR Review Loop

Automate Pull Request comment handling and code quality checks via GitHub API.

Community
Advanced
SensLiaoSensLiao

gsd-inbox

Review GitHub issues and pull requests against project templates and guidelines.

Community
Advanced