create-pr

Create pull requests with Conventional Commits validation and optional CI checks.

Updated Apr 14, 2025

Search Tags:#pull request #CI/CD #Git #Conventional Commits #PR creation

Ready to run

npx skills add https://github.com/vladpolewoi/config76 --skill create-pr-vladpolewoi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating pull requests, adhering to project conventions and the Conventional Commits spec, reducing manual steps and streamlining the PR workflow.

Core Features & Use Cases

Automated PR Creation: Stage changes, commit, push, and open a pull request following project conventions.
Optional Checks: Skip validation checks with skip-checks argument for quick PR creation.
Custom Branch Targeting: Allow users to specify the target branch for the PR.

Quick Start

Run the create-pr skill with the branch name you want to target. Example: create-pr "target-branch-name" --ticket VGV-123.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate pull request creation with Conventional Commits?▼

To automate pull request creation with Conventional Commits, this Skill stages changes, validates commit messages against the spec, pushes to your Git hosting platform, and opens a PR. It reduces manual steps by handling branch selection and PR description generation.

How do I create a pull request targeting a specific branch?▼

You can create a pull request targeting a specific branch by running the command with your target branch name, like `create-pr "target-branch-name"`. The Skill handles staging, committing, pushing, and opening the PR to that designated base branch.

Does PR creation require a working Git environment?▼

Yes, automated PR creation requires a working Git environment and knowledge of Conventional Commits. The Skill operates by executing Git commands to stage, commit, and push changes directly within your local repository setup.

Can I skip validation checks for quick pull request creation?▼

Yes, you can skip validation checks for quick pull request creation by using the `skip-checks` argument. This bypasses the Conventional Commits validation and optional CI checks, allowing you to rapidly stage and push changes.

What is the best way to handle Conventional Commits validation before pushing?▼

The best way to handle Conventional Commits validation is using an automated workflow that validates commit messages before pushing. This Skill checks your staged changes against the spec, pushes valid commits, and optionally runs CI checks to ensure compliance.

Why does my pull request workflow need Conventional Commits?▼

Your pull request workflow needs Conventional Commits to standardize commit history and automate release notes. This Skill enforces the specification during PR creation, ensuring project conventions are met before changes are merged into the target branch.