// 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".
[HINT] 下载包含 SKILL.md 和所有相关文件的完整技能目录
| name | labeling-android-changes |
| description | 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". |
PR titles and commit messages must include a conventional commit type keyword. This keyword drives automatic t: label assignment via CI (.github/workflows/sdlc-label-pr.yml).
The type keyword appears after the Jira ticket prefix:
[PM-XXXXX] <type>: <imperative summary>
| 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 |
Infer the type from the task description and changes made. If the type cannot be confidently determined, ask the user.
The CI labeling script matches <type>: or <type>( in the lowercased PR title, so the keyword must be followed by a colon or parenthesis. CI also accepts additional aliases (e.g., revert, bugfix, cleanup). See .github/label-pr.json for the full mapping.
