skilld
All skills
bitwarden avatar

/labeling-changes

@71bbb4f official
by bitwardenbitwarden/ai-plugins155 stars
20

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

  • 1 file
  • 2.8 KB
  • Updated 6 days ago
  • GitHub

Ask your Agent

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

This session only. Nothing lands on disk.

SKILL.md

≈76 tokens always: the name and description. ≈627 when used: this file.

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

Return the chosen type keyword and the t: label it maps to.

Format

The type keyword appears after the Jira ticket prefix:

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

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

Type Keywords

Type Label Use for
feat t:feature New features or functionality
fix t:bug Bug fixes
refactor t:tech-debt Code restructuring without behavior change
chore t:tech-debt Maintenance, cleanup, minor tweaks
test t:tech-debt Adding or updating tests
perf t:tech-debt Performance improvements
docs t:docs Documentation changes
ci / build t:ci CI/CD and build system changes
deps t:deps Dependency updates
llm t:llm LLM/Claude configuration changes
breaking t:breaking-change Breaking changes requiring migration
misc t:misc Changes that do not fit other categories

CI also accepts additional aliases (e.g., revert, bugfix, cleanup). See .github/label-pr.json for the full mapping.

Selecting a Type

Infer the type from the task description and changes made. If the type cannot be confidently determined, ask the user.

Ambiguous Cases

  • Refactor that incidentally fixes a bug → use the primary intent: fix: if the bug was the goal, refactor: if the restructuring was the goal
  • Adding tests for existing untested code → test: (not chore:)
  • Updating a dependency to fix a vulnerability → deps: (not fix:)
  • Changing Claude/LLM configuration files → llm: (not chore:)
  • Removing dead code → refactor: (not chore: — it changes the codebase structure)

Source: SKILL.md on GitHub

Third-party checks

No third-party reports yet.

Provenance

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

Last checked against GitHub 20 hours ago.

Activeupdated 6 days ago

Topics

  • conventional-commits
  • ci
  • labeling
  • github-actions
  • jira
  • pr-automation

README badge

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

What it does

Enforces conventional commit type keywords in PR titles and commit messages, enabling automated label assignment via CI. Install this skill when titling commits or PRs in Bitwarden's workflow — it provides the type keyword reference and selection guidance for ambiguous cases.

Generated from the current SKILL.md.

Frequently asked

What conventional commit types does this skill support?
The skill references a table in `change-type-labels.md` with type keywords and CI label mappings. Consult that file for the full list and guidance on selecting a type for ambiguous cases.
How does the CI labeling script match the type keyword?
The script matches `<type>:` or `<type>(` in the lowercased PR title, so the keyword must be followed by a colon or parenthesis.
What should I do if the change type is ambiguous?
Ask the user to clarify the change type rather than guessing. The skill is designed to prompt for user input when the type cannot be confidently determined.
Where does the type keyword go in the commit message?
The type keyword appears after the Jira ticket prefix: `[PM-XXXXX] <type>: <imperative summary>`.

Generated from the current SKILL.md. These answers refresh after source changes.