Name: create-pr
Author: wix-incubator

Prompt file imported from wix-incubator/obsidian (.cursor/commands/create-pr.md). Copyright stays with the author.

Open a PR

Important: Steps 2 and 3 require required_permissions: ['all'] because:

Pre-commit hooks need access to global npm/node paths outside the workspace
gh CLI has TLS certificate issues in sandboxed mode

Step 1: Check state (ONE command)

git branch --show-current && git status -s && git diff HEAD --stat

Always create a new branch for each PR unless you're already on the correct branch for the current changes.
If on main OR if the current branch doesn't match the work you're committing: create a branch using the appropriate prefix:
- feat/<description> - new features
- fix/<description> - bug fixes
- chore/<description> - maintenance, refactoring, etc.

git checkout -b feat/<description>

Note: git checkout -b requires required_permissions: ['git_write']

Step 2: Commit + Push (`required_permissions: ['all']`)

If uncommitted changes exist:

If staged files exist (respect user's selection):

git commit -m "<msg>" && git push

If unstaged files exist (add specific files, NOT git add .):

git add <file1> <file2> ... && git commit -m "<msg>" && git push

Step 3: Create PR (`required_permissions: ['all']`)

Format:

<feature_area>: <Title> (80 chars max)

<TLDR> (1-2 sentences)

- bullet 1
- bullet 2

Without skip-review:

gh pr create --title "<title>" --body "<body>"

With skip-review (user says "skip review", "#skipreview", etc.):

gh pr create --title "<title>" --body "<body>" && gh pr comment $(gh pr view --json number -q .number) --body "#skipreview #forcemerge"

With force-merge (user says "foce merge", "#forcemerge", etc.):

gh pr create --title "<title>" --body "<body>" && gh pr comment $(gh pr view --json number -q .number) --body "#skipreview #forcemerge"

Display the returned PR URL as a markdown link on its own line, formatted as: [PR #<number>](<url>) so it's clickable. Display the name of the branch you created.

Install create-pr and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Open a PR Important: Steps 2 and 3 require `required_permissions: ['all']` because: - Pre-commit hooks need access to global npm/node paths outside the workspace - `gh` CLI has TLS certificate issues in sandboxed mode ## Step 1: Check state (ONE command) ```bash git branch --show-current && git status -s && git diff HEAD --stat ``` - **Always create a new branch for each PR** unless you're already on the correct branch for the current changes. - If on `main` OR if the current branch doesn't match the work you're committing: create a branch using the appropriate prefix: - `feat/<description>` - new features - `fix/<description>` - bug fixes - `chore/<description>` - maintenance, refactoring, etc. ```bash git checkout -b feat/<description> ``` Note: `git checkout -b` requires `required_permissions: ['git_write']` ## Step 2: Commit + Push (`required_permissions: ['all']`) If uncommitted changes exist: **If staged files exist** (respect user's selection): ```bash git commit -m "<msg>" && git push ``` **If unstaged files exist** (add specific files, NOT `git add .`): ```bash git add <file1> <file2> ... && git commit -m "<msg>" && git push ``` ## Step 3: Create PR (`required_permissions: ['all']`) **Format:** ``` <feature_area>: <Title> (80 chars max) <TLDR> (1-2 sentences) - bullet 1 - bullet 2 ``` **Without skip-review:** ```bash gh pr create --title "<title>" --body "<body>" ``` **With skip-review** (user says "skip review", "#skipreview", etc.): ```bash gh pr create --title "<title>" --body "<body>" && gh pr comment $(gh pr view --json number -q .number) --body "#skipreview #forcemerge" ``` **With force-merge** (user says "foce merge", "#forcemerge", etc.): ```bash gh pr create --title "<title>" --body "<body>" && gh pr comment $(gh pr view --json number -q .number) --body "#skipreview #forcemerge" ``` Display the returned PR URL as a markdown link on its own line, formatted as: `[PR #<number>](<url>)` so it's clickable. Display the name of the branch you created.

{ "prompt": "# Open a PR\n\nImportant: Steps 2 and 3 require `required_permissions: ['all']` because:\n- Pre-commit hooks need access to global npm/node paths outside the workspace\n- `gh` CLI has TLS certificate issues in sandboxed mode\n\n## Step 1: Check state (ONE command)\n\n```bash\ngit branch --show-current && git status -s && git diff HEAD --stat\n```\n\n- **Always create a new branch for each PR** unless you're already on the correct branch for the current changes.\n- If on `main` OR if the current branch doesn't match the work you're committing: create a branch using the appropriate prefix:\n - `feat/<description>` - new features\n - `fix/<description>` - bug fixes\n - `chore/<description>` - maintenance, refactoring, etc.\n\n```bash\ngit checkout -b feat/<description>\n```\n\nNote: `git checkout -b` requires `required_permissions: ['git_write']`\n\n## Step 2: Commit + Push (`required_permissions: ['all']`)\n\nIf uncommitted changes exist:\n\n**If staged files exist** (respect user's selection):\n```bash\ngit commit -m \"<msg>\" && git push\n```\n\n**If unstaged files exist** (add specific files, NOT `git add .`):\n```bash\ngit add <file1> <file2> ... && git commit -m \"<msg>\" && git push\n```\n\n## Step 3: Create PR (`required_permissions: ['all']`)\n\n**Format:**\n```\n<feature_area>: <Title> (80 chars max)\n\n<TLDR> (1-2 sentences)\n\n- bullet 1\n- bullet 2\n```\n\n**Without skip-review:**\n```bash\ngh pr create --title \"<title>\" --body \"<body>\"\n```\n\n**With skip-review** (user says \"skip review\", \"#skipreview\", etc.):\n```bash\ngh pr create --title \"<title>\" --body \"<body>\" && gh pr comment $(gh pr view --json number -q .number) --body \"#skipreview #forcemerge\"\n```\n\n**With force-merge** (user says \"foce merge\", \"#forcemerge\", etc.):\n```bash\ngh pr create --title \"<title>\" --body \"<body>\" && gh pr comment $(gh pr view --json number -q .number) --body \"#skipreview #forcemerge\"\n```\n\nDisplay the returned PR URL as a markdown link on its own line, formatted as: `[PR #<number>](<url>)` so it's clickable.\nDisplay the name of the branch you created.", "variables": [], "notes": "Important: Steps 2 and 3 require `required_permissions: ['all']` because: - Pre-commit hooks need access to global npm/node paths outside the workspace - `gh` CLI has TLS certificate issues in sandboxed mode", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/wix-incubator/obsidian", "path": ".cursor/commands/create-pr.md", "ref": "8aff448838ae62e39b2b5c3c2fabbe466136c86d", "url": "https://github.com/wix-incubator/obsidian/blob/8aff448838ae62e39b2b5c3c2fabbe466136c86d/.cursor/commands/create-pr.md", "key": "wix-incubator/obsidian/.cursor/commands/create-pr.md" } } }

create-pr

About

Open a PR

Step 1: Check state (ONE command)

Step 2: Commit + Push (`required_permissions: ['all']`)

Step 3: Create PR (`required_permissions: ['all']`)

Install create-pr and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews

About

Open a PR

Step 1: Check state (ONE command)

Step 2: Commit + Push (required_permissions: ['all'])

Step 3: Create PR (required_permissions: ['all'])

Install create-pr and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews

Step 2: Commit + Push (`required_permissions: ['all']`)

Step 3: Create PR (`required_permissions: ['all']`)