Committing Changes
- 40 installs
- 129 repo stars
- Updated August 4, 2026
- bitwarden/ai-plugins
Committing Changes is a Claude skill that defines Bitwarden's git commit message format and workflow, including the Jira ticket prefix and conventional type keyword.
About
This skill defines git commit conventions and workflow for Bitwarden repositories. It specifies a commit message format with a [PM-XXXXX] Jira ticket prefix, a conventional type keyword, and an optional body, plus rules for follow-up commits and a pre-commit quality gate. A developer uses it when committing code, writing commit messages, or preparing changes for commit in a Bitwarden repo.
- Commit message format with Jira ticket prefix and conventional type keyword
- Rules for first vs follow-up commits on a branch
- Points to a pre-commit quality gate before staging
Committing Changes by the numbers
- 40 all-time installs (skills.sh)
- Ranked #323 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
committing-changes capabilities & compatibility
- Capabilities
- git commit · commit message
- Works with
- github · jira
- Use cases
- documentation
What committing-changes says it does
Git commit conventions and workflow for Bitwarden repositories.
Only the first commit on a branch needs the full format (ticket prefix, type keyword, body).
npx skills add https://github.com/bitwarden/ai-plugins --skill committing-changesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 40 |
|---|---|
| repo stars | ★ 129 |
| Last updated | August 4, 2026 |
| Repository | bitwarden/ai-plugins ↗ |
What it does
Write Bitwarden commit messages with the correct ticket prefix, type, and format.
Who is it for?
Writing correctly formatted Bitwarden commit messages with ticket prefix and conventional type.
Skip if: Repositories outside Bitwarden's PM-ticket and CI-label conventions.
When should I use this skill?
You are committing code, writing a commit message, or preparing changes for commit in a Bitwarden repo.
What you get
Commits follow the [PM-XXXXX] type: summary format with the correct type and a pre-commit quality gate.
- Conventionally formatted Bitwarden commit message
By the numbers
- Requires [PM-XXXXX] Jira ticket prefix on the first commit
Files
Git Commit Conventions
Commit Message Format
[PM-XXXXX] <type>: <imperative summary>
<optional body explaining why, not what>Rules
1. Ticket prefix: Always include [PM-XXXXX] matching the Jira ticket 2. 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 casesFollowup 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.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
What is the commit message format?
[PM-XXXXX] <type>: <imperative summary> with an optional body explaining why, not what.
Do follow-up commits need the full format?
No. Only the first commit on a branch needs the ticket prefix, type keyword, and body; later commits can use a short descriptive summary.