Index of every page on this site: llms.txt
All skills
bitwarden avatar

/committing-changes

@a11c77b official
by bitwardenbitwarden/ai-plugins165 stars
27
Run it yourself

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

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

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

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈258 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill provides Git commit conventions and branch management guidelines for Bitwarden repositories. It includes a testing harness in Python to evaluate triggering behavior. The analysis found no malicious behavior, and the identified technical patterns are consistent with standard developer tooling.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

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

Last checked against GitHub yesterday.

Activeupdated 2 months ago
All 1 allowed tools
Skill(labeling-changes)
  • Git/VCS
  • commit
  • jira
  • conventions
  • bitwarden
  • workflow
  • commit-messages
  • version-control

README badge

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

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.

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.