PR Finalize Review
microsoft/garnet
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.
Conventional commit type keywords for PR titles and commit messages.
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwarden/ai-plugins labeling-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "labeling-changes" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changes into .claude/skills/labeling-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "labeling-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwarden/ai-plugins labeling-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/bitwarden-delivery-tools/skills/labeling-changes .agents/skills/labeling-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "labeling-changes" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changes into .agents/skills/labeling-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "labeling-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwarden/ai-plugins labeling-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/bitwarden-delivery-tools/skills/labeling-changes .cursor/skills/labeling-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "labeling-changes" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changes into .cursor/skills/labeling-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "labeling-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bitwarden/ai-plugins.git --path plugins/bitwarden-delivery-tools/skills/labeling-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwarden/ai-plugins labeling-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/bitwarden-delivery-tools/skills/labeling-changes .gemini/skills/labeling-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "labeling-changes" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changes into .gemini/skills/labeling-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "labeling-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bitwarden/ai-plugins labeling-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/bitwarden-delivery-tools/skills/labeling-changes .github/skills/labeling-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "labeling-changes" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changes into .github/skills/labeling-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "labeling-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwarden/ai-plugins --skill labeling-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwarden/ai-plugins labeling-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/bitwarden-delivery-tools/skills/labeling-changes .opencode/skills/labeling-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "labeling-changes" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-delivery-tools/skills/labeling-changes into .opencode/skills/labeling-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "labeling-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
labeling-changesConventional 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. 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.
Read from SKILL.md and the folder at commit 0047fdf. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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).”
Just SKILL.md in plugins/bitwarden-delivery-tools/skills/labeling-changes of bitwarden/ai-plugins.
Open the folder on GitHubat commit 0047fdf
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Labeling Changes this skillbitwarden/ai-plugins | 154 | — | ~707 | Automated safety check: Pass | Custom licence | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Gh PR Metadatamodule-federation/core | 2.7k | — | ~1k | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 |
microsoft/garnet
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.
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.
verdaccio/verdaccio
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.
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.
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.
tisfeng/Easydict
创建或复用当前 checkout 已提交变更的 GitHub PR,必要时推送任务分支。PR 审查使用 review-pr;仅本地提交使用 git-commit。
bitwarden/ai-plugins
Reviews Claude configuration files for security, structure, and prompt engineering quality.
bitwarden/ai-plugins
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…
bitwarden/ai-plugins
This skill should be used when the user asks to "review the security architecture", "check authentication patterns", "evaluate trust boundaries", "review encryption implementation", "assess…
bitwarden/ai-plugins
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.
bitwarden/ai-plugins
Audit GitHub Actions action usage across an org. An agent skill from bitwarden/ai-plugins.
bitwarden/ai-plugins
Remediate GitHub Actions action findings identified by the action-audit skill.
Works with
Categories
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.
Labeling Changes fits situations like: determining the change type for commits; another delivery skill asks for the type keyword and its t: label.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Labeling Changes is instructions for the agent only.
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.
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.
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.
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.
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.
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.