mcpbeat

Create Pull Request

bitwarden/create-pull-request

Pull request creation workflow for Bitwarden Clients. 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".

403 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
13507
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/bitwarden/clients --skill create-pull-request

The instruction itself

6 sections, as written by the author

Create Pull Request

PR Title Format

[PROJ-XXXXX] Short imperative summary

Examples:

  • [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

  • All tests pass: Run npm test
  • Lint clean: Run npm run lint
  • No unintended changes: Check git diff origin/main...HEAD for unexpected files
  • 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

How to use it

Copy the folder

Take bitwarden/create-pull-request from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.