How do I install the Committing Changes skill?

Run npx skillmds@latest add bitwarden/committing-changes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Committing Changes safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Committing Changes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Committing Changes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Committing Changes?

bitwarden (@bitwarden) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Committing Changes by bitwarden — Agent Skill

Name: Committing Changes
Rating: 4.2 (5 reviews)
Author: bitwarden

Committing Changes

Git commit conventions and workflow for Bitwarden repositories. Use when committing code, writing commit messages, or preparing changes for commit. Triggered by "commit", "git commit", "commit message", "prepare commit", "stage changes".

bitwarden c311776 7 files · 27.2 KB Updated Sep 10, 2026

File contents

Git Commit Conventions

Branch Check

Resolve the repository's default branch from the remote rather than assuming main. If the current branch is the default, ask for a branch name before staging or committing. Offer to suggest one and confirm before switching. If the default branch cannot be resolved, say so and confirm the current branch is intended before staging.

Commit Message Format

[PM-XXXXX] <type>: <imperative summary>

<optional body explaining why, not what>

Rules

Ticket prefix: Always include [PM-XXXXX] matching the Jira ticket
Type keyword: Read ${CLAUDE_PLUGIN_ROOT}/references/change-type-labels.md for the full table of conventional commit types and their CI label mappings. If the type cannot be confidently determined, ask the user.

Examples

[PM-12345] feat: Add biometric unlock timeout configuration

Users reported confusion about when biometric prompts appear.
This adds a configurable timeout setting to the security preferences.

Ambiguous cases — choosing between similar types:

# Refactor that also fixes a bug? Use the primary intent:
[PM-12345] fix: Resolve null pointer in vault sync retry logic

# Test-only change:
[PM-12345] test: Add unit tests for biometric timeout edge cases

Followup Commits

Only the first commit on a branch needs the full format (ticket prefix, type keyword, body). Subsequent commits can use a short, descriptive summary with no prefix or body required.

Update error handling in login flow

Pre-Commit Quality Gate

Before staging, run the perform-preflight skill for the full quality gate checklist (tests, lint, security, architecture). Consult the repo's CLAUDE.md for platform-specific build and lint commands.

---name: committing-changesdescription: Git commit conventions and workflow for Bitwarden repositories. Use when committing code, writing commit messages, or preparing changes for commit. Triggered by "commit", "git commit", "commit message", "prepare commit", "stage changes".---# Git Commit Conventions## Branch CheckResolve the repository's default branch from the remote rather than assuming `main`. If the current branch is the default, ask for a branch name before staging or committing. Offer to suggest one and confirm before switching. If the default branch cannot be resolved, say so and confirm the current branch is intended before staging.## Commit Message Format```[PM-XXXXX] <type>: <imperative summary><optional body explaining why, not what>```### Rules1. **Ticket prefix**: Always include `[PM-XXXXX]` matching the Jira ticket2. **Type keyword**: Read `${CLAUDE_PLUGIN_ROOT}/references/change-type-labels.md` for the full table of conventional commit types and their CI label mappings. **If the type cannot be confidently determined, ask the user.**### Examples```[PM-12345] feat: Add biometric unlock timeout configurationUsers reported confusion about when biometric prompts appear.This adds a configurable timeout setting to the security preferences.```Ambiguous cases — choosing between similar types:```# Refactor that also fixes a bug? Use the primary intent:[PM-12345] fix: Resolve null pointer in vault sync retry logic# Test-only change:[PM-12345] test: Add unit tests for biometric timeout edge cases```### Followup CommitsOnly the first commit on a branch needs the full format (ticket prefix, type keyword, body). Subsequent commits can use a short, descriptive summary with no prefix or body required.```Update error handling in login flow```---## Pre-Commit Quality GateBefore staging, run the `perform-preflight` skill for the full quality gate checklist (tests, lint, security, architecture). Consult the repo's CLAUDE.md for platform-specific build and lint commands.

Frequently asked questions