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

/commit-message

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

Abacus land.commit slot for Bitwarden. Compose one commit's subject and body for a change Abacus is about to land, following bitwarden-delivery-tools:committing-changes, with settled rules for work that has no Jira ticket and for followup commits. Used by Abacus's land.commit workflow stage, not invoked by people directly.

Use this Skill: https://skilld.dev/gh/bitwarden/ai-plugins/commit-message

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈85 tokens for metadata: the name and description. ≈456 when used: this file.

Description uses 4.3% 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 ≈341 characters, or 4.3%.

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.

Commit message (Abacus land.commit, Bitwarden)

Abacus calls this from its land.commit stage, which gives you the change, the bead's title, its source (the issue or ticket the work tracks, or none) and each acceptance criterion with its evidence.

  1. Invoke Skill(bitwarden-delivery-tools:committing-changes) and follow its commit message format, type keyword and body rules.
  2. The ticket prefix, settled here so the stage never stops to ask:
    • When the bead's source is a Jira ticket (a key such as PM-1234, or a bitwarden.atlassian.net/browse/ link), use that key: [PM-1234].
    • Otherwise (a GitHub issue, any other link, or no source), drop the bracket entirely: <type>: <imperative summary>. Never invent a ticket key or write a placeholder in its place.
  3. Every commit uses the full format. The skill's followup-commit exemption (a short summary with no prefix or body after a branch's first commit) does not apply here: Abacus lands unattended, so each commit it makes carries the ticket prefix (when there is a ticket), the type keyword and a body, whatever precedes it on the branch.
  4. Compose the message only. The Abacus stage records it, and abacus-finalize commits it and appends Abacus's own trailers, so leave trailers out. Skip the skill's steps that act: the stage already settles the branch (it is Abacus's) and the pre-commit checks (the gate and the reviewer have run), and staging or committing belongs to abacus-finalize.

Pull request titles are not covered here. Abacus's land.pr slot uses bitwarden-abacus-tools:composing-abacus-pull-requests, which follows bitwarden-delivery-tools:applying-pr-conventions. That skill drops the bracket the same way when there is no ticket, so a bead's commit subject and pull request title agree.

Source: SKILL.md on GitHub

No rule matched.

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 alerts28d3 checks · Risk SAFE
  • Gen Agent Trust Hub28d

    The skill provides instructions for generating standardized commit messages for Bitwarden's Abacus automation tool. It defines logic for handling Jira ticket prefixes and commit bodies by referencing an internal Bitwarden delivery tool. It contains no executable code, network operations, or security risks.

  • Socket28d

    No alerts

  • Snyk28d

    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 5 days ago
All 1 allowed tools
Skill(bitwarden-delivery-tools:committing-changes)

README badge

README badge for bitwarden/ai-plugins/commit-message