pr-creator

Create pull requests from repository templates via the GitHub CLI.

2|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/bl1nk-bot/agent-library --skill pr-creator-bl1nk-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/bl1nk-bot/agent-library/tree/main/.gemini/skills/pr-creator
Command: npx skills add https://github.com/bl1nk-bot/agent-library --skill pr-creator-bl1nk-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users in producing high-quality Pull Requests that consistently follow repository templates and standards, reducing manual PR formatting effort and errors.

Core Features & Use Cases

  • Workflow-guided PR creation: ensures proper branch naming, template selection, and PR description formatting.
  • Template adherence: locates and applies PR templates from the repository (.github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md).
  • Preflight checks & submission: prompts you to run checks (lint, tests) and submits the PR via the CLI using the required title format.

Quick Start

  • Check current branch: git branch --show-current
  • If on main, create and switch to a new branch: git checkout -b <new-branch-name>
  • Locate PR templates: .github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md
  • Read template and draft description following its structure
  • Preflight checks: cargo check && cargo test
  • Create PR with gh: gh pr create --title "type(scope): succinct description" --body-file <temp_file_path>
  • Remove temp file
  • Title style: Use Conventional Commits if your repo uses it, e.g., feat(server): add new endpoint

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 that follows repository templates?

Automating pull request creation involves locating templates like .github/pull_request_template.md, drafting a compliant description, running preflight checks, and submitting via the GitHub CLI with a properly formatted title.

What is the best way to ensure my PR description matches the repository template?

To ensure your PR description matches the template, locate the pull request template file in the .github directory, read its required structure, draft your description accordingly, and pass it to gh pr create using a temporary body file.

How do I create a pull request via the GitHub CLI with a conventional commit title?

Creating a pull request via the GitHub CLI requires running gh pr create with a title formatted as type(scope): description, such as feat(server): add new endpoint, while attaching your template-based description as the body.

Do I need to run preflight checks before submitting a pull request?

Running preflight checks before submitting a pull request is required to verify code quality; the workflow prompts you to execute lint and test commands like cargo check and cargo test prior to using the GitHub CLI for submission.

Can I use this workflow to handle branch naming and PR submission together?

Handling branch naming and PR submission together is supported; the workflow guides you to check your current branch, create a new one if you are on main, and then submit the pull request via the GitHub CLI.

Why does my pull request submission fail when using a template body file?

Pull request submission may fail if the temporary body file path is incorrect or if the title does not follow the required conventional commit format; ensure the file is properly generated and removed after submission.