open-prlisted

Open a pull request (Azure DevOps or GitHub) for the current branch, giving it a title and description that follow the CALLER's own conventions — learned at runtime from their past merged PRs — with a ticket link and a description of what changed and why. Use whenever someone wants to open / raise / put up a PR, finish a branch, or send changes for review on Azure DevOps or GitHub, even if they don't say "open-pr". It always shows the title and description for confirmation first and never creates the PR without explicit approval. Trigger phrases: "open a PR", "raise a PR", "create a pull request", "put this up for review", "PR this branch", "backport this to a release line", "open-pr", "/open-pr". Do NOT trigger for: reviewing or summarizing an existing PR; triaging or replying to PR comments (that is a separate resolve-pr-comments skill); completing / merging a PR; starting a branch; or plain git operations.
softwareone-platform/issue-to-pr · ★ 1 · Code & Development · score 67

Install: claude install-skill softwareone-platform/issue-to-pr

# Open PR Open a pull request for the current branch on the detected PR platform (Azure DevOps or GitHub). The title and description are drafted to match **the caller's own previous PRs**, read off the repo's own history — falling back to everyone's PRs, and then to no convention at all — rather than a fixed house style, then shown for confirmation. The PR is **never created without explicit approval** — opening a PR is an outward-facing action. This skill is backend-agnostic: the platform-specific mechanics (create PR, dup-check, label, merged-PRs query, PR cross-reference link) live in **backend adapter reference docs** under `resources/backends/`, and the ticket-link mechanics live in **tracker adapter reference docs** under `resources/trackers/`. The skill body detects platform and tracker, loads the matching adapters, and follows their recipes — it holds **no `az`/`gh`-specific field parsing and no tracker-specific id/URL parsing** of its own. It borrows the safety rails of a PR-creation flow but is deliberately narrower: it opens a PR for the branch **as it is** — publishing it to the remote first where the remote does not have it, or does not yet have its newest commits, since the PR carries what the remote branch holds. It does not merge the base branch in, does not delete branches, and does not triage review comments (that is `resolve-pr-comments`). ## Step 0 — Detect platform + tracker, load adapters, announce Before anything else, resolve which backend and trac