Pull request creation workflow for Bitwarden repositories. Use when creating PRs, writing PR descriptions, or preparing branches for review. Triggered by "create PR", "pull request", "open PR", "gh pr create", "PR description".
How this skill is triggered — by the user, by Claude, or both
Slash command
/bitwarden-delivery-tools:creating-pull-requestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
[PM-XXXXX] <type>: <short imperative summary>
Type keywords (triggers automatic t: label via CI): read ${CLAUDE_PLUGIN_ROOT}/references/change-type-labels.md for the full table.
Examples:
[PM-12345] feat: Add autofill support for passkeys[PM-12345] fix: Resolve crash during vault sync[PM-12345] refactor: Simplify authentication flowAlways follow the repo's PR template at .github/PULL_REQUEST_TEMPLATE.md. Read it and fill in each section. If no template exists, use this fallback:
## 🎟️ Tracking
<!-- Paste the link to the Jira or GitHub issue or otherwise describe / point to where this change is coming from. -->
## 📔 Objective
<!-- Describe what the purpose of this PR is, for example what bug you're fixing or new feature you're adding. -->
## 📸 Screenshots
<!-- Required for any UI changes; delete if not applicable. Use fixed width images for better display. -->
Delete the Screenshots section entirely if there are no UI changes.
Before creating, run perform-preflight if not already done.
git push -u origin <branch-name>
gh pr create --draft --title "[PM-XXXXX] feat: Short summary" --body "<fill in from PR template>"
Default to draft PRs. Only create a non-draft PR if the user explicitly requests it.
Before running gh pr create, always use the AskUserQuestion tool to ask whether to add an AI review label:
ai-review-vnext, ai-review, No labelIf the user selects a label, include it via the --label flag:
gh pr create --draft --label "ai-review-vnext" --title "..." --body "..."
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
npx claudepluginhub denobotion/ai-plugins --plugin bitwarden-delivery-tools