# Git Create Pr

> Create or update a reviewable pull request for the intended branch. Use when the user types /git-create-pr.

- Skill: `blockmatic/git-create-pr` (Agent Skill)
- Install (CLI): `npx skillmds@latest add blockmatic/git-create-pr`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blockmatic/git-create-pr/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: blockmatic (https://skillmd.com/u/blockmatic)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/blockmatic/git-create-pr

---


## Purpose and inputs

Invocation requests publishing the intended branch and creating its PR. Inspect the base, branch diff, relevant issue, existing PR, and repository template first.

## Steps

1. Ensure task-owned changes are committed and validated using the repository's checks. Use [git-commit](../git-commit/SKILL.md) if needed, preserving unrelated work.
2. Push the intended branch using [git-push](../git-push/SKILL.md).
3. Write a standalone description: problem, resulting behavior, verification evidence, and material limitations. Follow the repository template; never create an empty description. Use a conventional PR title when the repository requires it. Keep a `BREAKING CHANGE:` footer in the body when required so squash-merge preserves it.
4. Reuse an existing PR for this branch rather than duplicating it. Use known applicable labels and requested reviewers; do not invent assignments.
5. With a CLI, write multiline text to a temporary file and pass the body-file option. Verify the resulting title, base, and description.

## Verification and handoff

- [ ] Correct source and target branches and a nonempty, accurate description.
- [ ] Validation claims match observed results; remaining blockers are explicit.
- [ ] PR URL resolves to the intended change.

Return the PR link. PR creation does not authorize merge or deployment.