# pr-create

> Creates GitHub pull requests with conventional commit-style titles. Use when creating PRs, submitting changes for review, or when user says /pr, /pr-create.

- Author: Darien Hernández González
- Repository: dohernandez/claude-skills
- Version: 20260126182826
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/dohernandez/claude-skills
- Web: https://mule.run/skillshub/@@dohernandez/claude-skills~pr-create:20260126182826

---

---
name: pr-create
description: Creates GitHub pull requests with conventional commit-style titles. Use when creating PRs, submitting changes for review, or when user says /pr, /pr-create.
user-invocable: true
allowed-tools: [Bash, Read, Grep, Glob]
hooks:
  Stop:
    - type: command
      command: "task -t .claude/Taskfile.yaml validate-skill -- --skill pr-create"
---

# PR Create

## Purpose
Creates GitHub pull requests with conventional commit-style titles and structured bodies.
Follows the project's git workflow conventions from `.claude/docs/git-workflow.md`.

## Quick Reference
- Creates: GitHub PR via `gh pr create`
- Requires: GitHub CLI installed and authenticated, committed changes on a feature branch
- Stop hook: `task -t .claude/Taskfile.yaml validate-skill -- --skill pr-create`

## Prerequisites

Before creating a PR, verify:
1. **gh CLI installed**: `gh --version` - if missing: `brew install gh`
2. **gh CLI authenticated**: `gh auth status` - if not: `gh auth login`

## PR Title Format

```
<type>(<scope>): <subject>
```

### Types

| Type | Use for |
|------|---------|
| `feat` | New features |
| `fix` | Bug fixes |
| `chore` | Maintenance, refactoring |
| `docs` | Documentation |
| `test` | Test changes |
| `perf` | Performance improvements |
| `ci` | CI/CD changes |

### Scopes

Scopes are optional and project-specific. Common patterns:
- Module/package names (e.g., `auth`, `api`, `db`)
- Feature areas (e.g., `config`, `logging`)
- Service names (e.g., `worker`, `gateway`)

### Title Rules

1. Max 50 characters
2. Capitalized first letter after colon
3. No period at the end
4. Be specific - avoid "improve", "enhance", "update"
5. **NO AI ATTRIBUTION** - STRICTLY FORBIDDEN

## AI Attribution Policy

**COMPLETE VIOLATION** - Never include ANY of the following in PR titles, bodies, or commits:
- `Co-Authored-By: Claude`, `Co-Authored-By: GPT`, or any AI name
- AI-related emojis
- "Generated by", "Created with", or similar phrases
- Any reference to AI tools (Claude, ChatGPT, Copilot, etc.)

PRs and commits must appear as human-authored work. This is a strict framework requirement.

## PR Body Template

Use the PR template at `.github/PULL_REQUEST_TEMPLATE.md`.

The framework installs a default template to `.github/` if the project doesn't have one.

Standard format:

```markdown
## Description

[2-3 sentences summarizing what changed]

## Types of Changes

- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Chore (maintenance tasks, refactoring, or non-functional changes)

## Checklist

- [ ] My code follows the code style of this project
- [ ] I have added the necessary documentation (if appropriate)
- [ ] I have added tests (if appropriate)
- [ ] Lint and unit tests pass locally with my changes
```

## User Review Step

Before creating the PR, present it to the user for review:

```
## PR Preview

**Title:** feat(auth): Add OAuth2 login support

**Body:**
## Description

Adds OAuth2 authentication via Google and GitHub providers.
Users can now log in with their existing accounts.

## Types of Changes

- [ ] Bug fix
- [x] New feature
...

---
Any changes I should make?
```

Wait for user confirmation:
- If user says "no" or confirms → create the PR
- If user requests changes → incorporate feedback and show again

## Automation
See `skill.yaml` for the full procedure and patterns.
See `sharp-edges.yaml` for common failure modes.