skilld
All skills
bitwarden avatar

/committing-changes

@71bbb4f official
by bitwardenbitwarden/ai-plugins155 stars
20

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".

Ask your Agent

Use this Skill: https://skilld.dev/gh/bitwarden/ai-plugins/committing-changes

This session only. Nothing lands on disk.

SKILL.md

≈64 tokens always: the name and description. ≈411 when used: this file. ≈4.5k more on demand in 5 files.

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

  1. Ticket prefix: Always include [PM-XXXXX] matching the Jira ticket
  2. Type keyword: Invoke Skill(labeling-changes) to pick the conventional commit type.

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.

Source: SKILL.md on GitHub

Third-party checks

No alerts14d3 checks · Risk SAFE
  • Gen Agent Trust Hub14d

    The skill provides Git commit conventions and workflow automation for Bitwarden repositories. It includes an evaluation runner in the evals directory for benchmarking skill performance during development. The skill follows best practices by requiring user confirmation for significant actions like branch switching and commit creation.

  • Socket14d

    No alerts

  • Snyk14d

    Risk: LOW · No issues

Provenance

Signed by skilld at 71bbb4f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 6 days ago

Capability

All 1 allowed tools
Skill(labeling-changes)

Topics

  • Git/VCS
  • commit
  • jira
  • conventions
  • bitwarden
  • workflow
  • commit-messages
  • version-control

README badge

README badge for bitwarden/ai-plugins/committing-changes

What it does

Defines commit message conventions for Bitwarden repositories, including mandatory Jira ticket prefixes, conventional commit types tied to CI labels, and optional explanatory bodies. Use when staging changes or writing commit messages to ensure consistency with the Bitwarden workflow and CI pipeline.

Generated from the current SKILL.md.

Frequently asked

Do I need to include the Jira ticket prefix in every commit on a branch?
No. Only the first commit on a branch requires the full format with ticket prefix, type keyword, and body. Subsequent commits can use a short descriptive summary.
What if I'm not sure which commit type to use?
The skill references a change-type-labels.md file with the full table of conventional commit types. If you still cannot confidently determine the type, ask the user before committing.
Does this apply to all Bitwarden repositories?
Yes. This skill covers Git commit conventions and workflow for Bitwarden repositories generally, though you should also consult the repo's CLAUDE.md for any platform-specific guidance.
What should I do before committing code?
Run the perform-preflight skill to check tests, lint, security, and architecture. Consult the repo's CLAUDE.md for platform-specific build and lint commands.

Generated from the current SKILL.md. These answers refresh after source changes.