create-pr

Name: create-pr
Availability: InStock
Author: tecnologia-ibtech

Create GitHub pull requests with conventional-commit titles and Jira references.

Updated Mar 29, 2026

Search Tags:#automation #git #github #jira #pr #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill create-pr-tecnologia-ibtech

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes PR titles and bodies across Geovendas repositories by generating GitHub pull requests using Conventional Commits, reducing review time and inconsistencies.

Core Features & Use Cases

Generate PR titles in the Conventional Commits format (e.g., feat(vue): add user search) and enforce structured scopes for Geovendas projects.
Create PR bodies that include a Jira reference, summary, and a checklist, helping reviewers understand changes quickly.
Detect the correct base branch, identify current changes, and support choosing between regular PRs or draft PRs.
Supported scopes include vaadin6, vue, vaadin23, pedidos, dotnet, etl, b2b, geochat, entity, service, repo, lib, api.

Quick Start

Ask Claude to generate a PR for a specific task using a conventional-commit title for the targeted Geovendas repository.

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 conventional commits?▼

Automating GitHub pull request creation with conventional commits involves generating structured PR titles and bodies that include a type, scope, and Jira reference. This standardizes changes across repositories to reduce review time and inconsistencies.

How do I link a Jira ticket to a GitHub PR body automatically?▼

To link a Jira ticket to a GitHub PR body automatically, the pull request generation process extracts the ticket reference and embeds it within the PR body alongside a summary and checklist, ensuring reviewers can quickly track the associated task.

Can I generate a draft PR using conventional commit formatting?▼

Yes, you can generate a draft PR using conventional commit formatting. The automation process supports choosing between regular pull requests and draft PRs while applying the required type and scope structure to the title.

What is the correct scope for conventional commit titles in multi-project repositories?▼

The correct scope for conventional commit titles in multi-project repositories is determined by predefined project identifiers such as vue, dotnet, pedidos, or api. This targeted scoping ensures changes are correctly categorized for each specific codebase.

Does the PR automation detect the correct base branch automatically?▼

Yes, PR automation detects the correct base branch automatically. It identifies current changes and verifies the target branch before creating the pull request, guiding the user through the necessary verification steps to ensure accurate merging.

Why use conventional commits for pull request titles?▼

Using conventional commits for pull request titles enforces a standardized format like feat(vue): add feature, which clarifies the change type and scope. This structure reduces review time and eliminates inconsistencies across multiple development projects.