git-pr-creation

Create a GitHub pull request from the current branch into dev with a structured body.

14|1|Updated Oct 23, 2025

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

Ready to run

npx skills add https://github.com/marcioaltoe/claude-craftkit --skill git-pr-creation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-pr-creation
Source: https://github.com/marcioaltoe/claude-craftkit/tree/main/plugins/git/skills/git-pr-creation
Command: npx skills add https://github.com/marcioaltoe/claude-craftkit --skill git-pr-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive pull requests from feature branches into dev, with well-structured descriptions and proper commit context.

Core Features & Use Cases

PR Drafting: Generate well-formatted PR titles and bodies following a standardized template.
Authentication & Context: Verify gh authentication and current branch, ensure PR against dev.
Automation of CI Context: Surface relevant changes, tests status, and impact analysis.

Quick Start

Use the gh CLI to draft and create a PR from your current branch into dev with a well-structured body.

Frequently Asked Questions about git-pr-creation

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

FAQPage Schema

How do I automate creating pull requests with proper commit summaries?▼

This Skill automates PR creation from feature branches into dev, automatically analyzing commits with git log and enforcing Conventional Commits style. It generates structured PR titles and bodies using a standardized template, eliminating manual formatting.

What's required before I can create a PR using gh CLI automation?▼

You need gh CLI authenticated, a feature or fix branch with commits following Conventional Commits format, and push access to your repository. The Skill verifies authentication and current branch context before creating the PR.

How does Conventional Commits formatting improve pull request quality?▼

Conventional Commits enforce a consistent message structure (type, scope, description) that makes commit history readable and enables automated changelog generation. This Skill applies that standard to PR titles and bodies for clarity and traceability.

Can I use this to create PRs into branches other than dev?▼

This Skill is designed specifically to create PRs targeting the dev branch. For other target branches, alternative automation or manual PR creation may be needed.

What happens if my commits don't follow Conventional Commits format?▼

The Skill enforces Conventional Commits style, so commits that deviate will cause validation to fail. Rebase and amend your commits to match the required format (feat:, fix:, refactor:, etc.) before triggering PR creation.

Does this integrate with CI checks before opening the PR?▼

The Skill surfaces CI context and test status in the PR body to help reviewers understand change impact. It does not block PR creation based on CI results; those checks run after submission.