Agent Skills › makeplane/plane › branch-name

branch-name

GitHub

用于生成符合规范的 Git 分支名称，支持新建或重命名。遵循 type/work-item-id-description 格式，兼容 PR 技能提取工作项 ID，确保命名规范与可追溯性。

.claude/skills/branch-name/SKILL.md makeplane/plane

触发场景

用户请求创建新分支用户请求重命名现有分支

安装

npx skills add makeplane/plane --skill branch-name -g -y

更多选项

非标准路径

npx skills add https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name -g -y

不安装直接使用

npx skills use makeplane/plane@branch-name

指定 Agent (Claude Code)

npx skills add makeplane/plane --skill branch-name -a claude-code -g -y

安装 repo 全部 skill

npx skills add makeplane/plane --all -g -y

预览 repo 内 skill

npx skills add makeplane/plane --list

SKILL.md

Frontmatter

{
    "name": "branch-name",
    "description": "Use when starting a new branch or renaming an existing one — produces a branch name in the format `<type>\/<work-item-id>-<short-description>` that's compatible with the create-pr skill's work item ID extraction.",
    "user_invocable": true
}

Branch Naming

Create branch names that follow the convention <type>/<work-item-id>-<short-description>, where the work item ID can be cleanly extracted later (e.g., by the create-pr skill).

Format

<type>/<work-item-id>-<short-description>

All lowercase, hyphen-separated
Work item ID stays in its original form but lowercased (e.g., SILO-1146 → silo-1146)
Short description is 2–5 words in kebab-case, focused on the what, not the how

Workflow

Determine the type based on the work being done:
- feat — new functionality
- fix — bug fix
- chore — tooling, deps, config, non-user-facing housekeeping
- refactor — restructuring without behavior change
- docs — documentation only
- perf — performance improvement
Determine the work item ID:
- If the user gives one, use it
- If they reference a Plane work item (e.g., a URL or title), extract the ID
- If none exists, ask the user — don't invent one
Write the short description:
- 2–5 words in kebab-case
- Describe the outcome, not the implementation (add-app-tile-visibility, not update-tile-component)
- Skip filler words (the, a, for)
Assemble and create the branch:

   git checkout -b <type>/<work-item-id-lowercased>-<short-description>

Return the branch name to the user.

Examples

fix/silo-1146-relative-config-urls
feat/web-1234-app-tile-visibility
chore/web-2201-bump-eslint
refactor/silo-980-extract-auth-middleware
docs/web-1500-pr-template-update
perf/silo-1310-cache-workspace-lookup

Common Mistakes

Putting the work item ID at the end instead of after the type (breaks extraction)
Using underscores or camelCase instead of hyphens
Uppercasing the work item ID inside the branch name (it should be lowercase here, uppercased only when used as the PR title prefix)
Writing a long, narrative description — keep it scannable
Omitting the work item ID when one exists in Plane
Using a type that won't match the eventual PR type (pick the type you'd use in the PR title)