Labeling Changes

bitwarden/labeling-changes

Conventional commit type keywords for PR titles and commit messages. Use when determining the change type for commits or PRs. Triggered by "what type", "label", "change type", "conventional commit", "t: label".

257 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

129

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/bitwarden/ai-plugins --skill labeling-changes

The instruction itself

3 sections, as written by the author

Labeling Changes

PR titles and commit messages must include a conventional commit type keyword. This keyword drives automatic t: label assignment via CI (.github/scripts/label-pr.py reads .github/label-pr.json).

Format

The type keyword appears after the Jira ticket prefix:

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

Type Keywords and Selection Guidance

Read ${CLAUDE_PLUGIN_ROOT}/references/change-type-labels.md for the full table of type keywords, their CI label mappings, and guidance for selecting a type (including ambiguous cases).

The CI labeling script matches <type>: or <type>( in the lowercased PR title, so the keyword must be followed by a colon or parenthesis. If the type cannot be confidently determined, ask the user.

How to use it

Copy the folder

Take bitwarden/labeling-changes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.