pr

Create pull requests after passing formatting, linting, and test checks.

4|Updated Dec 31, 2025

Search Tags:#automation #git #quality #pr #ci #pull-requests

Ready to run

npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill pr-taketo-yoda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/Taketo-Yoda/uv-sbom/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill pr-taketo-yoda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates PR creation with mandatory pre-flight checks to ensure code quality and consistent formatting before opening a pull request.

Core Features & Use Cases

Pre-flight checks: format, clippy, and tests must pass before PR creation.
Branch hygiene: verifies not on main and enforces naming conventions.
Base branch decision and PR creation: determines target base and uses gh pr create with a templated message.
Automated feedback: provides actionable guidance when checks fail and can re-run after fixes.

Quick Start

Trigger the PR workflow by issuing the /pr command to begin pre-flight checks and PR creation.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I automate pull request creation with pre-flight checks for formatting and tests?▼

Automating pull request creation with pre-flight checks requires verifying formatting, linting, and test success before opening a PR. This workflow enforces branch hygiene, determines the base branch, pushes changes, and creates the PR using gh pr create with a templated message.

What happens if my formatting or linting checks fail before creating a pull request?▼

When formatting or linting checks fail before creating a pull request, the workflow halts PR creation and provides automated feedback with actionable guidance. Users can apply the suggested fixes and re-run the pre-flight checks to verify branch status and proceed.

Can I use this to enforce branch naming conventions and prevent commits to main?▼

Yes, enforcing branch naming conventions and preventing direct commits to main are core branch hygiene features. The workflow verifies you are not on the main branch and enforces naming conventions before determining the target base branch and proceeding with PR creation.

What's the best way to ensure CI readiness before opening a pull request?▼

The best way to ensure CI readiness before opening a pull request is running mandatory pre-flight checks that enforce formatting, linting, and test success. This approach verifies branch status and guarantees code quality standards are met before using gh pr create.

Do I need the GitHub CLI to automate PR creation with pre-flight checks?▼

Yes, the GitHub CLI is needed to automate PR creation with pre-flight checks. The workflow specifically uses the gh pr create command to push changes and open a pull request with a templated message after formatting, linting, and test validations pass.

How do I determine the correct base branch when automating a pull request?▼

To determine the correct base branch when automating a pull request, the pre-flight workflow evaluates your current branch status and repository structure. It identifies the appropriate target base branch, enforces naming conventions, and then pushes changes before executing gh pr create.