# Create Draft PR

Commit, push, and create a draft PR using the pr-description format, with UX flow...

- Repository: https://github.com/trycompai/crm (11793 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add trycompai/crm --skill create-draft-pr -g -a claude-code -y`
Codex: `npx skills add trycompai/crm --skill create-draft-pr -g -a codex -y`
Cursor: `npx skills add trycompai/crm --skill create-draft-pr -g -a cursor -y`
Gemini CLI: `npx skills add trycompai/crm --skill create-draft-pr -g -a gemini-cli -y`

## Description

Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create Draft PR

Commit all changes, push to remote, and create a draft pull request with a focused generated description.

## Steps

1. Run `git status` to see changes
2. Run `git diff` to understand what changed
3. Run `git log` to see commit message style
4. If on `main`, create a new branch in the format `<initials>/<feature>` or the project's branch naming convention, then switch to it
5. Stage and commit changes with a concise message
6. Push branch to remote with `-u` flag
7. Generate the PR description using the `pr-description` skill's description format.
8. If the change is user-facing, workflow-oriented, or architectural, include a concise UX flow section using the `ux-flow-plan` style.
9. Create draft PR using `gh pr create --draft`
10. If you created the branch (were on `main`), switch back to `main` after the PR is created

## PR Body Format

Use the `pr-description` skill's format as the base:

```markdown
## Summary

<One sentence describing the overall change>

- Additional note if needed
- Another note if needed

## Problem

Describe the issue being addressed. What was broken, missing, or suboptimal? Be specific about the root cause.

## Solution

Explain the approach taken to fix the problem. Include code snippets only when they clarify the core approach.
```

When relevant, add this section between `Problem` and `Solution`:

````markdown
## UX Flow

```text
Current flow
└─ ...

Desired flow
└─ ...
```
````

Only include `UX Flow` when it helps explain the product behavior, user journey, or architecture boundary. Keep it short and use the `ux-flow-plan` tree style.

## Rules

The rest: https://github.com/trycompai/crm/blob/HEAD/.agents/skills/create-draft-pr/SKILL.md