菜单
Set up branch and folder naming rules for the current project
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Connect to the running Redmine instance and log in via the Playwright MCP browser, using REDMINE_PLAYRIGHT_URL/REDMINE_PLAYRIGHT_USER/REDMINE_PLAYRIGHT_PASSWORD environment variables. Use whenever the user asks to open, check, access, or test something in the running Redmine UI (e.g. verifying a feature in the browser, taking a screenshot of a page, manually exercising a flow).
Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.
Create or update the feature specification from a natural language feature description.
| name | speckit-branch-convention-configure |
| description | Set up branch and folder naming rules for the current project |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"branch-convention:commands/speckit.branch-convention.configure.md"} |
Set up configurable naming rules for how /specify creates Git branches and spec folder names. Supports ticket IDs, GitFlow prefixes, date formats, and custom patterns.
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty). The user may specify a preset (e.g., "gitflow", "ticket", "date") or provide custom patterns directly.
.specify/ directory.specify/branch-convention.ymlDetermine convention type: Based on user input or interactive selection:
| Preset | Branch Pattern | Folder Pattern | Example Branch | Example Folder |
|---|---|---|---|---|
default | {seq}-{kebab} | {seq}-{kebab} | 003-user-auth | 003-user-auth |
gitflow | {type}/{seq}-{kebab} | {seq}-{kebab} | feat/003-user-auth | 003-user-auth |
ticket | {ticket}-{kebab} | {ticket}-{kebab} | PROJ-142-user-auth | PROJ-142-user-auth |
date | {date}-{kebab} | {date}-{kebab} | 20260408-user-auth | 20260408-user-auth |
custom | User-defined pattern | User-defined pattern | — | — |
Collect configuration: Build the convention config with these fields:
# .specify/branch-convention.yml
convention:
branch_pattern: "{type}/{seq}-{kebab}"
folder_pattern: "{seq}-{kebab}"
type_prefix:
feature: "feat"
bugfix: "fix"
hotfix: "hotfix"
refactor: "refactor"
docs: "docs"
default_type: "feat"
seq_padding: 3
seq_start: 1
date_format: "YYYYMMDD"
ticket_pattern: "[A-Z]+-[0-9]+"
max_length: 60
separator: "-"
lowercase: true
Available tokens: Document these template tokens for patterns:
| Token | Description | Example |
|---|---|---|
{seq} | Zero-padded sequence number | 003 |
{kebab} | Kebab-case feature summary (2-4 words) | user-auth-flow |
{ticket} | Ticket/issue ID (e.g., JIRA, Linear) | PROJ-142 |
{date} | Date in configured format | 20260408 |
{type} | Branch type prefix from type_prefix map | feat |
{summary} | Raw feature summary (spaces allowed) | user auth flow |
Write configuration: Save the convention to .specify/branch-convention.yml
Validate existing branches (optional): If branches already exist, check them against the new convention and report any non-compliant ones.
Report: Output a summary:
/speckit.branch-convention.validate to check compliance, or /speckit.specify to create a new feature using the convention.specify/branch-convention.yml already exists, show current config and ask before replacingfeat/) while folder stays flat{seq}-{kebab}) applies/, -, _)