pr-creator

Creates GitHub pull requests following repository templates and branch safety rules.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/bkrsna/gemini-cli --skill pr-creator-bkrsna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/bkrsna/gemini-cli/tree/main/.gemini/skills/pr-creator
Command: npx skills add https://github.com/bkrsna/gemini-cli --skill pr-creator-bkrsna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating pull requests manually often leads to inconsistent descriptions, ignored templates, accidental commits to the main branch, and failed CI checks discovered only after the PR is opened. This Skill enforces a disciplined, repeatable PR creation workflow. ## Core Features & Use Cases - Branch Safety Enforcement: Verifies you are not on the main branch before committing or pushing, and creates a new branch when needed. - Template Compliance: Locates the repository's pull request template (e.g., .github/pull_request_template.md) and drafts a description that follows its headings and checklists. - Preflight Validation: Runs the workspace preflight script (npm run preflight) so build, lint, and test checks pass before the PR is created. - Use Case: After finishing a bug fix, ask the assistant to open a PR. It commits your changes on a feature branch, fills in the template, links the related issue, pushes the branch, and creates the PR with the gh CLI using a Conventional Commits title. ## Quick Start Create a pull request for my current changes following the repository's PR template.

Frequently Asked Questions about pr-creator

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use the gh CLI with gh pr create, passing a title and a body file via --body-file to avoid shell escaping issues with multi-line Markdown. Push your branch first with git push -u origin HEAD.

How do I follow a repository pull request template automatically?

Locate the template at .github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md, read its structure, and draft the PR body keeping all headings and checklists. Mark completed items with [x] and link related issues.

What happens if I try to create a PR from the main branch?

The workflow blocks it. It checks the current branch with git branch --show-current, and if it is main, it creates and switches to a new descriptive branch before committing or pushing anything.

Does the PR creation workflow run tests before opening the PR?

Yes. It runs npm run preflight as a preflight check covering build, lint, and test steps. If any check fails, the issues must be fixed before the PR is created.

What title format should a pull request use?

When the repository uses Conventional Commits, the PR title follows the type(scope): description format, such as feat(ui): add new button or fix(core): resolve crash.