Name: open-pr
Author: rflpazini

Imported from rflpazini/agents-skills (cursor-skills/open-pr/SKILL.md). Install upstream with npx skills add rflpazini/agents-skills --skill open-pr. Copyright stays with the author.

Open PR

Title Format

[TICKET_KEY]: Short imperative summary

Examples:

[STCBE-1077]: Introduce UserAccountUpdateNotifier
[STCBE-842]: Fix race condition in session refresh
[PCAD-310]: Remove deprecated PlutoSync v1 endpoints

Extract the ticket key from the branch name (e.g. feature/STCBE-1077-notifier → STCBE-1077). If the branch has no ticket key, ask the user.

Body

Check for a PR template: look for .github/pull_request_template.md or PULL_REQUEST_TEMPLATE.md in the repo root. If found, follow its structure.
Write a brief summary at the top — short bullet points describing what changed. Focus on the what and why, skip the how. One bullet per logical change, 1-2 lines each.
Fill checklists from the template honestly. Check items that apply, leave unchecked items with a short reason if needed.

Example summary:

- Add `UserAccountUpdateNotifier` interface to decouple service layer from transport details
- Centralize account-update Kafka publishing through `UserAccountService.updateUserAccount()`
- Remove direct `PlutoUserRegistrationKafkaPublisher` dependency from 4 call-sites
- Resolves cyclic dependency flagged by Sonar

Workflow

Run git status and git log to understand what's being shipped
If a Jira ticket key is available, fetch the ticket via MCP for extra context
Compose title and body following the rules above
Push the branch with git push -u origin HEAD
Create the PR as draft with gh pr create --draft --title "..." --body "..."
Return the PR URL to the user

{ "ocm": "1", "id": "rflpazini-agents-skills-open-pr", "kind": "skill", "name": "open-pr", "description": "Create pull requests with consistent formatting. Use when the user asks to open a PR, create a PR, submit a PR, or push and create a pull request. Enforces title convention [TICKET_KEY]: summary, follows the repo's pull_request_template.md if present, and writes a concise bullet-point description of what changed and why.", "publisher": "rflpazini", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Create pull requests with consistent formatting. Use when the user asks to open a PR, create a PR, submit a PR, or push and create a pull request. Enforces title convention [TICKET_KEY]: summary, follows the repo's pull_request_template.md if present, and writes a concise bullet-point description of what changed and why." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/rflpazini/agents-skills", "path": "cursor-skills/open-pr/SKILL.md", "ref": "69d9fda0efbe854d33bb9aa942998dd9b558095c", "url": "https://github.com/rflpazini/agents-skills/blob/69d9fda0efbe854d33bb9aa942998dd9b558095c/cursor-skills/open-pr/SKILL.md", "key": "rflpazini/agents-skills/cursor-skills/open-pr/SKILL.md" } }, "instructions": "# Open PR\n\n## Title Format\n\n```\n[TICKET_KEY]: Short imperative summary\n```\n\nExamples:\n- `[STCBE-1077]: Introduce UserAccountUpdateNotifier`\n- `[STCBE-842]: Fix race condition in session refresh`\n- `[PCAD-310]: Remove deprecated PlutoSync v1 endpoints`\n\nExtract the ticket key from the branch name (e.g. `feature/STCBE-1077-notifier` → `STCBE-1077`).\nIf the branch has no ticket key, ask the user.\n\n## Body\n\n1. **Check for a PR template**: look for `.github/pull_request_template.md` or `PULL_REQUEST_TEMPLATE.md` in the repo root. If found, follow its structure.\n2. **Write a brief summary** at the t", "cost": { "context_tokens": 400 } }

open-pr

About

Open PR

Title Format

Body

Workflow

Use it

Manifest

Reviews