pr-creator_skill

This skill guides you to create compliant pull requests by following templates, checks, and conventional commits.

TypeScript
Official

92.6k

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill google-gemini/gemini-cli --skill pr-creator

SKILL.md2.8 KB

Overview

This skill automates creation of pull requests that match the repository's established templates and standards. It guides branch handling, template selection, draft generation, preflight checks, and uses the gh CLI to create the PR with a template-compliant description. The goal is consistent, review-ready PRs that pass build and lint checks before opening.

How this skill works

It inspects the current git branch and enforces working off a non-main branch. It locates and reads repository PR templates (common locations under .github) and generates a description that preserves template headings, checklists, and structure. It recommends running the workspace preflight script, then writes the final markdown to a temporary file and launches gh pr create using --body-file to avoid escaping issues.

When to use it

When asked to open a new pull request for code changes
When preparing a PR for bug fixes, features, or documentation updates
When the repository enforces PR templates or Conventional Commits
Before merging changes that must pass CI, linting, or test requirements
When creating PRs from the terminal using the gh CLI

Best practices

Always verify current branch with git branch --show-current and create a descriptive feature branch if on main
Locate and read the exact PR template file in .github and follow its headings and checklist items
Mark checklist items truthfully; do not check boxes for incomplete tasks
Run npm run preflight (or the project’s preflight script) and fix failures before creating the PR
Use Conventional Commits style for the PR title when the repo requires it (e.g., feat(scope): short summary)

Example use cases

Implementing a new CLI command and opening a feature PR that follows the feature template
Fixing a TypeScript runtime error and opening a bug_fix PR that links the related issue
Updating README or docs and ensuring the documentation PR template is followed
Refactoring core logic, running preflight to ensure tests/lint pass, and creating a conventionally formatted PR title

FAQ

Select the template that best matches the change (feature vs bug). If ambiguous, ask which template the user prefers or choose the most relevant file under .github/PULL_REQUEST_TEMPLATE/.

How do I avoid markdown escaping issues when creating the PR?

Write the drafted description to a temporary file and call gh pr create --body-file <temp_file_path>, then remove the temp file after creating the PR.