pr-creator

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating pull requests manually often leads to inconsistent descriptions, ignored templates, accidental commits to main, and failed CI checks. This Skill enforces a disciplined workflow so every PR follows the repository's established standards. ## 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 and reads the repository's pull request template (e.g., .github/pull_request_template.md) and drafts a description that follows its structure, headings, and checklists. - Preflight Validation: Runs the workspace preflight script (npm run preflight) to confirm build, lint, and test checks pass before creating the PR. - Use Case: After finishing a bug fix, ask the assistant to create a PR. It commits your changes on a feature branch, fills out the template with linked issues, runs preflight checks, pushes the branch, and opens the PR via the gh CLI with a Conventional Commits title. ## Quick Start Ask the assistant to create a pull request for your current changes using 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 pull request that follows a repository template?

Locate the template in .github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md, read its structure, and draft a description that keeps all headings and checklists. Then create the PR with gh pr create using --body-file to avoid shell escaping issues.

How do I avoid committing directly to the main branch?

Run git branch --show-current to check your current branch. If it is main, create and switch to a new branch with git checkout -b <branch-name> before staging and committing any changes.

What should I do before creating a pull request?

Commit all intended changes, fill out the PR template completely, and run the workspace preflight script (npm run preflight) to verify build, lint, and test checks pass. Then push the branch and create the PR.

Why use gh pr create with --body-file instead of inline text?

Multi-line Markdown descriptions cause shell escaping problems when passed inline. Writing the description to a temporary file and passing it with --body-file preserves formatting, then the temporary file can be removed.

What title format should a pull request use?

Use the Conventional Commits format when the repository adopts it, such as feat(ui): add new button or fix(core): resolve crash. This keeps PR titles consistent and machine-parseable for changelogs.