
Create Pull Request
- 10 installs
- 13.5k repo stars
- Updated August 5, 2026
- bitwarden/clients
create-pull-request is a Claude Code skill defining the pull-request creation workflow, title format, and pre-PR checklist for the Bitwarden Clients repo.
About
This skill defines the pull-request creation workflow for the Bitwarden Clients repo. It sets a PR title format with the Jira ticket prefix, points to the repo PR template for the body, and enforces a pre-PR checklist covering tests, lint, an unintended-change check, and rebasing. A developer uses it when opening a PR or preparing a branch for review. It defaults to creating draft PRs.
- Standardizes PR title format with Jira prefix and imperative summary
- Enforces a pre-PR checklist (tests, lint, clean diff, rebased branch)
- Defaults to draft PRs following the repo PR template
Create Pull Request by the numbers
- 10 all-time installs (skills.sh)
- Ranked #431 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
create-pull-request capabilities & compatibility
- Capabilities
- pull request creation · pr description · branch prep · code review
- Works with
- github · jira
- Use cases
- code review · documentation
What create-pull-request says it does
Pull request creation workflow for Bitwarden Clients.
Keep under 70 characters total
npx skills add https://github.com/bitwarden/clients --skill create-pull-requestAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 13.5k |
| Last updated | August 5, 2026 |
| Repository | bitwarden/clients ↗ |
What it does
Open a Bitwarden Clients pull request with the correct title format, template body, and a pre-PR checklist, defaulting to draft.
Who is it for?
Opening a correctly formatted, checklist-passing draft PR in the Bitwarden Clients repo.
Skip if: Repos without the Jira-prefixed title convention or the Bitwarden PR template.
When should I use this skill?
When creating PRs, writing PR descriptions, or preparing branches for review.
What you get
A well-formatted draft PR with a template body created after tests and lint pass.
- Formatted PR title
- PR body from the repo template
- Pre-PR checklist run
By the numbers
- 4-item pre-PR checklist
- title under 70 characters
- draft PR by default
Files
Create Pull Request
PR Title Format
[PROJ-XXXXX] Short imperative summaryExamples:
[PM-12345] Add passkey support to vault item creation[CL-1124] Increase badge max-width[PM-33446] Ensure attachments are cleared on clone
Rules:
- Include the Jira ticket prefix (e.g.
PM-,CL-) - Keep under 70 characters total
- Use imperative mood in the summary
---
PR Body Template
IMPORTANT: Always follow the repo's PR template at .github/PULL_REQUEST_TEMPLATE.md. Add TODO items to the screenshots section for each scenario that should be captured if any.
---
Pre-PR Checklist
1. All tests pass: Run npm test 2. Lint clean: Run npm run lint 3. No unintended changes: Check git diff origin/main...HEAD for unexpected files 4. Branch up to date: Rebase on main if needed
---
Creating the PR
# Ensure branch is pushed
git push -u origin <branch-name>
# Create PR as draft by default (body follows .github/PULL_REQUEST_TEMPLATE.md)
gh pr create --draft --title "[PM-XXXXX] Short summary" --body "<fill in from PR template>"Default to draft PRs. Only create a non-draft (ready for review) PR if the user explicitly requests it.
---
Base Branch
- Default target:
main - Check with team if targeting a feature branch instead