skills.rest
sirius-cc-wu
sirius-cc-wuCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Create GitHub pull requests with standardized titles via gh CLI.

3|1|Updated Jan 13, 2026
Search Tags:#automation#github#code-review#pull-request#branch-name#pr-title
One-click install
npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill create-pr-sirius-cc-wu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/sirius-cc-wu/sirius-skills/tree/main/create-pr
Command: npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill create-pr-sirius-cc-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub pull requests with standardized, properly formatted titles to reduce manual errors and speed up code reviews.

Core Features & Use Cases

  • Standardized PR Titles: Enforce ID/Scope extraction from the branch and adheres to the required summary rules.
  • Plan Validation: Check for completion of plan.md before PR creation to guard against incomplete work.
  • One-Click PR Creation: Push the branch if needed and create a PR using gh CLI with a descriptive body template.
  • Guided PR Body: Provide sections like Description, Type of Change, and Testing guidance to improve review clarity.

Quick Start

From your current branch, create a PR with a concise, imperative summary in the required title format.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with standardized titles?▼

To automate GitHub pull request creation with standardized titles, this skill extracts IDs from your branch name and uses the gh CLI to generate a PR with a properly formatted title and descriptive body template.

What is the best way to enforce consistent PR titles for code review?▼

The best way to enforce consistent PR titles for code review is to automatically extract the scope and ID from your branch name, ensuring every pull request adheres to required summary rules without manual formatting.

How does plan.md validation work before creating a pull request?▼

Plan.md validation checks for the completion of your implementation plan before pull request creation, guarding against incomplete work by ensuring all planned tasks are finished before the branch is pushed.

Do I need the gh CLI installed to automate branch push and PR creation?▼

Yes, you need the gh CLI installed to automate branch push and PR creation, as this skill relies on it to push your current branch if needed and create the pull request with a guided descriptive body.

Can I use this automation for feature, bugfix, and refactor PRs?▼

Yes, you can use this automation for feature, bugfix, and refactor PRs, as it is applicable to standard software development workflows and formats the PR title and body based on your branch name.

What sections are included in the guided PR body for GitHub pull requests?▼

The guided PR body for GitHub pull requests includes Description, Type of Change, and Testing guidance sections, providing structured information to improve review clarity for your team.

Related Skills

Explore More Software Engineering Skills→
Noisemaker111Noisemaker111

warm-feature-flow

Prepare a clean Git workspace and draft PR pipeline for new features.

Community
Intermediate
NodeJSmithNodeJSmith
77

review-autofixes

Review autofix pull requests and triage findings for code changes.

Community
Advanced
modiqomodiqo
820

commit-convention

Validate commit messages and PR titles against the Conventional Commits standard.

Official
Basic
canpok1canpok1

create-pr

Create GitHub Pull Requests from current branch changes using Git and GitHub CLI.

Community
Intermediate