# Create Pr

> Create a GitHub PR with optional issue linking. Use after committing and pushing changes. Use when this capability is needed.

- Skill: `tomevault-io/create-pr-22` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/create-pr-22`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/create-pr-22/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/create-pr-22

---


# Create Pull Request

## Usage
`/create-pr` or `/create-pr #42` (with GitHub issue)

## Workflow

### 1. Gather Context
```bash
git log --oneline main..HEAD
git diff --stat main..HEAD
git branch --show-current
```

### 2. Extract Issue Reference (if provided)
- From argument: `#42` or issue URL
- From branch name: extract issue number pattern `^\d+-`
- If no issue found, create PR without issue link

### 3. Push Current Branch
```bash
git push -u origin $(git branch --show-current)
```

### 4. Create PR
```bash
gh pr create --title "short description" --body "$(cat <<'EOF'
## Summary
- Brief description of changes

## Issue
Closes #42

## Test Plan
- [ ] Manual testing steps
- [ ] yarn check:all passes

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
```

### 5. Return PR URL
Print the PR URL so the user can review it.

## Rules
- Keep title under 70 characters
- Always include Summary section
- Include issue link in body if available
- Include test plan
- Push before creating PR
- Never force-push to main

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/vultisig) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->