Prompt file imported from pavelsvitek/hired-ai (.cursor/commands/create-draft-pr.md). Copyright stays with the author.

Create Draft PR

Name: create-draft-pr
Author: pavelsvitek

Push to remote and create a draft pull request.

Steps

Run git status to see current state
Run git diff main...HEAD to understand what changed compared to main
Run git log main..HEAD to see the commits to be included
Push branch to remote with -u flag (do NOT commit any new changes)
Create draft PR using gh pr create --draft

PR Body Format

Problem / Intent

[Why this change exists - the problem being solved or feature being added]

Approach

[High-level concept of the solution - not a list of file changes]

Linear

https://linear.app/pavelsvitekcom/issue/PAV-XX

Replace PAV-XX with the real issue id (e.g. PAV-38).

Rules

PR title must start with one of: Feature:, Bug:, Task:, or Ops:
PR title must include the full Linear issue id in the form PAV-38 (see team pavelsvitek, key PAV)
PR title format: <Type>: PAV-XX - <succinct title>
Example: Feature: PAV-38 - Public job listing and apply flow
Extract PAV-123 (or a pav-123 segment) from the current branch name when present (examples: feature/PAV-38-public-job-listing, feature/pav-38-short-slug)
If the branch has no ticket id, ask the user once for the PAV- issue (or have them run the create-ticket project skill in .cursor/skills/create-ticket to add an issue in the hired.ai Linear project, then use that id)
The ## Linear link in the body must be https://linear.app/pavelsvitekcom/issue/PAV-XX with the same id as in the title
Do NOT include a summary of code changes or files modified
Do NOT include a test plan with checkboxes
Do NOT include "Generated with Claude Code" or similar footers
Keep the PR description concise and focused on intent and approach
Use HEREDOC for the PR body to preserve formatting

Shell Execution Rules

Both git push and gh pr create require required_permissions: ["all"] (not just full_network) to avoid TLS certificate errors in the sandbox
Do NOT use apostrophes or single quotes in the PR body text — they break the HEREDOC inside "$(cat <<'EOF' ... EOF)". Rewrite sentences to avoid them (e.g. "the user's email" → "the email of the user")

# Create Draft PR Push to remote and create a draft pull request. ## Steps 1. Run `git status` to see current state 2. Run `git diff main...HEAD` to understand what changed compared to `main` 3. Run `git log main..HEAD` to see the commits to be included 4. Push branch to remote with `-u` flag (do NOT commit any new changes) 5. Create draft PR using `gh pr create --draft` ## PR Body Format ## Problem / Intent [Why this change exists - the problem being solved or feature being added] ## Approach [High-level concept of the solution - not a list of file changes] ## Linear https://linear.app/pavelsvitekcom/issue/PAV-XX Replace `PAV-XX` with the real issue id (e.g. `PAV-38`). ## Rules - PR title must start with one of: `Feature:`, `Bug:`, `Task:`, or `Ops:` - PR title must include the full Linear issue id in the form `PAV-38` (see team **pavelsvitek**, key `PAV`) - PR title format: `<Type>: PAV-XX - <succinct title>` - Example: `Feature: PAV-38 - Public job listing and apply flow` - Extract `PAV-123` (or a `pav-123` segment) from the current branch name when present (examples: `feature/PAV-38-public-job-listing`, `feature/pav-38-short-slug`) - If the branch has no ticket id, **ask the user once** for the `PAV-` issue (or have them run the **create-ticket** project skill in `.cursor/skills/create-ticket` to add an issue in the **hired.ai** Linear project, then use that id) - The **## Linear** link in the body must be `https://linear.app/pavelsvitekcom/issue/PAV-XX` with the same id as in the title - Do NOT include a summary of code changes or files modified - Do NOT include a test plan with checkboxes - Do NOT include "Generated with Claude Code" or similar footers - Keep the PR description concise and focused on intent and approach - Use HEREDOC for the PR body to preserve formatting ## Shell Execution Rules - Both `git push` and `gh pr create` require `required_permissions: ["all"]` (not just `full_network`) to avoid TLS certificate errors in the sandbox - Do NOT use apostrophes or single quotes in the PR body text — they break the HEREDOC inside `"$(cat <<'EOF' ... EOF)"`. Rewrite sentences to avoid them (e.g. "the user's email" → "the email of the user")

{ "prompt": "# Create Draft PR\n\nPush to remote and create a draft pull request.\n\n## Steps\n\n1. Run `git status` to see current state\n2. Run `git diff main...HEAD` to understand what changed compared to `main`\n3. Run `git log main..HEAD` to see the commits to be included\n4. Push branch to remote with `-u` flag (do NOT commit any new changes)\n5. Create draft PR using `gh pr create --draft`\n\n## PR Body Format\n\n## Problem / Intent\n\n[Why this change exists - the problem being solved or feature being added]\n\n## Approach\n\n[High-level concept of the solution - not a list of file changes]\n\n## Linear\n\nhttps://linear.app/pavelsvitekcom/issue/PAV-XX\n\nReplace `PAV-XX` with the real issue id (e.g. `PAV-38`).\n\n## Rules\n\n- PR title must start with one of: `Feature:`, `Bug:`, `Task:`, or `Ops:`\n- PR title must include the full Linear issue id in the form `PAV-38` (see team **pavelsvitek**, key `PAV`)\n- PR title format: `<Type>: PAV-XX - <succinct title>`\n- Example: `Feature: PAV-38 - Public job listing and apply flow`\n- Extract `PAV-123` (or a `pav-123` segment) from the current branch name when present (examples: `feature/PAV-38-public-job-listing`, `feature/pav-38-short-slug`)\n- If the branch has no ticket id, **ask the user once** for the `PAV-` issue (or have them run the **create-ticket** project skill in `.cursor/skills/create-ticket` to add an issue in the **hired.ai** Linear project, then use that id)\n- The **## Linear** link in the body must be `https://linear.app/pavelsvitekcom/issue/PAV-XX` with the same id as in the title\n- Do NOT include a summary of code changes or files modified\n- Do NOT include a test plan with checkboxes\n- Do NOT include \"Generated with Claude Code\" or similar footers\n- Keep the PR description concise and focused on intent and approach\n- Use HEREDOC for the PR body to preserve formatting\n\n## Shell Execution Rules\n\n- Both `git push` and `gh pr create` require `required_permissions: [\"all\"]` (not just `full_network`) to avoid TLS certificate errors in the sandbox\n- Do NOT use apostrophes or single quotes in the PR body text — they break the HEREDOC inside `\"$(cat <<'EOF' ... EOF)\"`. Rewrite sentences to avoid them (e.g. \"the user's email\" → \"the email of the user\")", "variables": [], "notes": "Push and create a draft PR with a focused summary.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/pavelsvitek/hired-ai", "path": ".cursor/commands/create-draft-pr.md", "ref": "5df9c636134a280d75897965c92e86f12b231ac1", "url": "https://github.com/pavelsvitek/hired-ai/blob/5df9c636134a280d75897965c92e86f12b231ac1/.cursor/commands/create-draft-pr.md", "key": "pavelsvitek/hired-ai/.cursor/commands/create-draft-pr.md" } } }

create-draft-pr

About

Create Draft PR

Steps

PR Body Format

Problem / Intent

Approach

Linear

Rules

Shell Execution Rules

Use it

Manifest

Reviews