Official agent skill

Labeling Changes

by bitwarden in bitwarden/ai-plugins

Conventional commit type keywords for PR titles and commit messages.

OfficialCustom licenceAuto-check passedDevelopment

Install Labeling Changes

skills CLI
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitwarden/ai-plugins labeling-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bitwarden-delivery-tools/skills/labeling-changes .claude/skills/labeling-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
labeling-changes
GitHub stars
154
Token cost
~707 tokens
SKILL.md length
248 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Custom licence

At a glance

Conventional commit type keywords for PR titles and commit messages.

  • Determining the change type for commits
  • SKILL.md covers Format, Type Keywords and Selecting a Type
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Another delivery skill asks for the type keyword and its t: label

What it does

Labeling Changes is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Conventional commit type keywords for PR titles and commit messages. Use when determining the change type for commits or PRs, or when another delivery skill asks for the type keyword and its t: label. Triggered by "what type", "label", "change type", "conventional commit", "t: label".

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. It works with GitHub. The repository describes itself as: AI plugin marketplace.

When your agent uses it

  • Determining the change type for commits
  • Another delivery skill asks for the type keyword and its t: label

Example prompts

  • “what type”
  • “change type”
  • “conventional commit”
  • “/labeling-changes”

What it can do on your machine

Read from SKILL.md and the folder at commit 0047fdf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Labeling Changes loads about 707 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 248 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~707

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 248 words (~707 tokens).

“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).”

— opening of SKILL.md by bitwarden, Custom licence
name
labeling-changes

Read the full SKILL.md on GitHub

Files

Just SKILL.md in plugins/bitwarden-delivery-tools/skills/labeling-changes of bitwarden/ai-plugins.

Open the folder on GitHubat commit 0047fdf

Compare with similar skills

Labeling Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Labeling Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Labeling Changes this skillbitwarden/ai-plugins154—~707Automated safety check: PassCustom licence
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Gh PR Metadatamodule-federation/core2.7k—~1kAutomated safety check: PassMIT
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0

Similar skills

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Gh PR Metadata

    module-federation/core

    Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.

    2.7k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed
  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Submit PR

    tisfeng/Easydict

    创建或复用当前 checkout 已提交变更的 GitHub PR,必要时推送任务分支。PR 审查使用 review-pr;仅本地提交使用 git-commit。

    15k GitHub stars~595 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from bitwarden/ai-plugins

All 33 skills in this repo
  • Reviewing Claude Config

    bitwarden/ai-plugins

    Official

    Reviews Claude configuration files for security, structure, and prompt engineering quality.

    154 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • Managing Workflow Secrets

    bitwarden/ai-plugins

    Official

    Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…

    154 GitHub stars~4k tokensUpdated yesterday
    Auto-check passed
  • Official

    This skill should be used when the user asks to "review the security architecture", "check authentication patterns", "evaluate trust boundaries", "review encryption implementation", "assess…

    154 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Official

    Audits an external (third-party) Claude Code plugin pinned in this marketplace for security risk before it is vendored, and writes the report to a file for downstream posting.

    154 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Action Audit

    bitwarden/ai-plugins

    Official

    Audit GitHub Actions action usage across an org. An agent skill from bitwarden/ai-plugins.

    154 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Action Remediate

    bitwarden/ai-plugins

    Official

    Remediate GitHub Actions action findings identified by the action-audit skill.

    154 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Labeling Changes

What does Labeling Changes do?

Conventional commit type keywords for PR titles and commit messages. Labeling Changes is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Conventional commit type keywords for PR titles and commit messages.

When should I use Labeling Changes?

Labeling Changes fits situations like: determining the change type for commits; another delivery skill asks for the type keyword and its t: label.

How do I install Labeling Changes in Claude Code?

Run `npx skills add bitwarden/ai-plugins --skill labeling-changes -a claude-code`. Or copy the skill folder (plugins/bitwarden-delivery-tools/skills/labeling-changes in bitwarden/ai-plugins) into .claude/skills/labeling-changes in your project. Claude Code loads it when a task matches its description.

How do I install Labeling Changes in Codex?

Run `npx skills add bitwarden/ai-plugins --skill labeling-changes -a codex`. Or copy the skill folder (plugins/bitwarden-delivery-tools/skills/labeling-changes in bitwarden/ai-plugins) into .agents/skills/labeling-changes in your project. Codex loads it when a task matches its description.

Can I use Labeling Changes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwarden/ai-plugins --skill labeling-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/labeling-changes, .gemini/skills/labeling-changes, .github/skills/labeling-changes and .opencode/skills/labeling-changes in your project.

What does Labeling Changes need to run?

SKILL.md names no scripts, command-line tools or credentials: Labeling Changes is instructions for the agent only.

Does Labeling Changes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Labeling Changes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Labeling Changes use?

Labeling Changes has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Labeling Changes use?

About 707 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Labeling Changes?

Skills that share tags, products or a category with Labeling Changes: PR Finalize Review (microsoft/garnet, 12k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Gh PR Metadata (module-federation/core, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Labeling Changes?

bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ai-plugins, which has 154 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 6, 2026.

Source: bitwarden/ai-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.