pr-creator

Name: pr-creator
Availability: InStock
Author: leeoohoo

Create pull requests with repository templates and conventional commit titles via gh CLI.

1|Updated Jan 21, 2026

Search Tags:#automation #developer tools #code review #pull request #conventional commits #github

Ready to run

npx skills add https://github.com/leeoohoo/open_gemini_cli --skill pr-creator-leeoohoo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/leeoohoo/open_gemini_cli/tree/main/.gemini/skills/pr-creator
Command: npx skills add https://github.com/leeoohoo/open_gemini_cli --skill pr-creator-leeoohoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill ensures that all pull requests (PRs) are created following the repository's established templates and standards, improving code quality and review efficiency.

Core Features & Use Cases

Template Adherence: Automatically finds and uses the correct PR template.
Structured Descriptions: Guides the user to fill out PR descriptions according to template requirements, including headings, checklists, and issue linking.
Conventional Commits: Enforces title formatting for better commit history.
Use Case: When you've finished a new feature, use this skill to generate a PR description that includes all necessary sections like "What was changed?", "How to test?", and links to related issues, ensuring a smooth review process.

Quick Start

Use the pr-creator skill to draft a pull request description based on the repository's template.

Frequently Asked Questions about pr-creator

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

FAQPage Schema

How do I automate pull request creation using repository templates?▼

Automating pull request creation involves finding the repository's specific template and using the `gh` CLI to execute the PR command. This ensures descriptions include required headings, checklists, and issue links for compliant code review.

How do I format pull request titles to follow conventional commit standards?▼

Formatting pull request titles with conventional commits enforces strict title structuring for a cleaner commit history. This standardizes the PR naming convention before the pull request is actually created and submitted.

What is the best way to ensure my PR description includes all required sections?▼

To ensure a PR description includes all required sections, you should adhere to the repository's established template. This guides you to fill out comprehensive descriptions with necessary headings like "How to test" and related issue links.

Does this PR creation process work with GitHub CLI?▼

Yes, the pull request creation process executes directly via the GitHub CLI (`gh`). It uses the CLI to automate the submission of structured descriptions and conventionally formatted titles to the GitHub repository.

Why should I use a structured template for code review pull requests?▼

Using a structured template for pull requests improves code quality and review efficiency. It enforces consistent descriptions, ensuring reviewers receive all necessary context like changes, testing steps, and issue linking.

Can I link related issues automatically when creating a pull request?▼

Linking related issues is a core part of drafting a comprehensive pull request description. The template adherence process guides you to include these issue links before executing the final PR creation command.