create-pr

Create GitHub pull requests after running lint, typecheck, and test checks.

Updated May 11, 2025
One-click install
npx skills add https://github.com/rogsme/dotfiles --skill create-pr-rogsme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/rogsme/dotfiles/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/rogsme/dotfiles --skill create-pr-rogsme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating a pull request, ensuring that all necessary quality checks are performed before the PR is submitted.

Core Features & Use Cases

  • Automated Pre-PR Pipeline: Executes a series of checks (lint, typecheck, test) to ensure code quality.
  • Pull Request Creation: Handles the push and creation of a PR to the specified branch with metadata generation.
  • Error Handling: Stops the process if any phase fails and provides specific error messages.

Quick Start

Create a PR to the 'dev' branch with all necessary checks by using the command: !create-pr dev

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with continuous integration checks?

Automating GitHub pull request creation involves running quality checks like linters, type checkers, and test suites before pushing code. This process orchestrates the push and creates the PR to a specified branch only if all checks pass.

Do I need the GitHub CLI to automate PR creation?

Yes, automating PR creation requires both git and the GitHub CLI (gh) installed. These dependencies handle the underlying repository operations, branch targeting, and the actual pull request creation process.

What happens if a linter or test suite fails during PR creation?

If a linter, type checker, or test suite fails during the PR creation process, the pipeline stops immediately. It prevents the push and PR submission, providing specific error messages to help you fix the code quality issues.

How do I create a pull request to a specific branch with automated quality checks?

To create a pull request to a specific branch with automated quality checks, you execute a command targeting the branch name. This triggers the pre-PR pipeline to run lint, typecheck, and test validations before pushing and generating the PR.

Can I run type checks and test suites before submitting a pull request automatically?

Yes, an automated pre-PR pipeline executes configured type checks and test suites before submitting a pull request. This ensures code quality validation occurs prior to the push and pull request creation phase.

Why does my automated pull request pipeline fail before submission?

An automated pull request pipeline fails before submission when specific code quality checks encounter errors. The process halts the push and PR creation, returning specific error messages detailing which linter, type checker, or test phase failed.