Slash Command

/draft-pr

Create or update a draft pull request for review

Install

npx claudepluginhub automata-network/claude-plugins --plugin git-workflow

Allowed Tools

Bash(git *)Bash(gh *)

Prompt Preview

Create or update a draft pull request for the user's work.

**Don't allow PRs from main/master branches.**

1. Check for uncommitted changes - if any, suggest using /push-work first
2. Determine the main branch (main or master) to use as the base
3. Make sure branch is pushed and synced with the main branch
4. Check if PR already exists: `gh pr list --head <branch> --state all`
   - Parse the output to determine PR state (open/merged/closed)
5. Analyze all commits from the main branch to generate a good PR description
6. Create or update PR based on step 4:
   - **If no PR exists:** Create ...

Command Content

Other plugins with /draft-pr

/draft-pr

Interactive PR drafting with git-first context gathering

ReadGrepGlob+4

github-author

/draft-pr

Creates a draft PR that closes the GitHub issue from the branch name

kitchen-sink

/draft-pr

Draft a PR message for fork contributions

BashRead

balatro-mod-dev

/draft-pr

Generate standards-compliant PR title and description from branch changes

git-workflow

/draft-pr

Create a Draft Pull Request from the current branch using GitHub CLI.

sonnetBash(git rev-parse:*)Bash(git status:*)Bash(git branch:*)+9

git-workflow

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitNov 17, 2025

Actions

View Source View Plugin View on GitHub View README

Create or update a draft pull request for the user's work. **Don't allow PRs from main/master branches.** 1. Check for uncommitted changes - if any, suggest using /push-work first 2. Determine the main branch (main or master) to use as the base 3. Make sure branch is pushed and synced with the main branch 4. Check if PR already exists: `gh pr list --head <branch> --state all` - Parse the output to determine PR state (open/merged/closed) 5. Analyze all commits from the main branch to generate a good PR description 6. Create or update PR based on step 4: - **If no PR exists:** Create ...

Create or update a draft pull request for the user's work.

Don't allow PRs from main/master branches.

Check for uncommitted changes - if any, suggest using /push-work first
Determine the main branch (main or master) to use as the base
Make sure branch is pushed and synced with the main branch
Check if PR already exists: gh pr list --head <branch> --state all
- Parse the output to determine PR state (open/merged/closed)
Analyze all commits from the main branch to generate a good PR description
Create or update PR based on step 4:
- If no PR exists: Create new draft PR with gh pr create --base <main-branch> --draft --title "..." --body "..."
- If PR exists and is open: Update existing PR with gh pr edit <number> --title "..." --body "..."
- If PR exists and is merged/closed: Create new draft PR (don't update merged/closed PRs)
Show PR URL and next steps

Use heredoc for PR body to handle markdown properly.

PR description should include:

Summary of changes
List of what was modified
Testing considerations (if applicable)