pr-creator

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

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

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 standards before it is opened. ## 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 preserves its 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 open a PR. It commits your changes on a feature branch, fills in the template with a Conventional Commits title, pushes the branch, and creates the PR via the gh CLI. ## 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 body. For multi-line Markdown descriptions, write the body to a temporary file and use the --body-file flag to avoid shell escaping issues.

How do I follow a repository pull request template automatically?

Locate the template in .github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md, read its structure, and draft the PR body preserving 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 pushing from main as a safety rule. It checks the current branch with git branch --show-current and creates a new descriptive branch with git checkout -b before committing or pushing.

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.