create-pr

Enforce conventional commits and run quality gates before opening PRs via GitHub CLI.

130|15|Updated Dec 14, 2025

Search Tags:#github #branching #review #lint #pull-request #tests #conventional-commits

Ready to run

npx skills add https://github.com/jMerta/codex-skills --skill create-pr-jmerta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/jMerta/codex-skills/tree/main/create-pr
Command: npx skills add https://github.com/jMerta/codex-skills --skill create-pr-jmerta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers to produce PRs that are easy to review and safe to merge by enforcing small, scoped changes, green checks, and a clear PR description with validation steps.

Core Features & Use Cases

Branch naming guidance for descriptive topics and predictable workflows.
Enforce conventional commits in the PR history.
Run quality gates (lint/tests/build) to ensure green checks before merging.
Open PR with a filled description via GitHub CLI (gh pr create --fill).

Quick Start

Describe your PR goal and then use this workflow:

Create a descriptive branch name: feat/<topic> or fix/<topic>.
Make focused commits following Conventional Commits.
Run lint/tests/build to ensure green checks.
Push and open the PR with gh pr create --fill. If gh is not available, provide manual steps to open PR on GitHub.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I create a pull request with conventional commits and quality checks?▼

To create a pull request with conventional commits, you make focused commits following the standard, run lint and tests to ensure green checks, then push and open the PR using the GitHub CLI with a filled description.

What's the best way to structure branches for clean pull requests?▼

The best way to structure branches for clean pull requests is using descriptive naming like feat/<topic> or fix/<topic>, which ensures focused changes and predictable workflows for feature, fix, or chore tasks.

Do I need the GitHub CLI installed to open a pull request?▼

You do not strictly need the GitHub CLI installed to open a pull request. The workflow uses gh pr create --fill by default, but provides manual steps to open the PR on GitHub if the CLI is unavailable.

Why should I run lint and tests before opening a PR?▼

You should run lint and tests before opening a PR to enforce quality gates that ensure green checks. This guarantees the changes are safe to merge and guides reviewers through consistent validation steps.

How does enforcing conventional commits improve pull request reviews?▼

Enforcing conventional commits improves pull request reviews by standardizing the PR history, which helps reviewers understand the scope of changes and validate feature, fix, or chore workflows consistently.