菜单
This skill should be used when the user invokes /git-helper:generate-branch, asks to "create a branch name", "name my branch", "what should I name this branch", "suggest a branch name", "what prefix should I use", "what branch should I create for this", "branch for ticket
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user invokes /debugging-workflow:parallel-debug, asks to "debug in parallel", "try all hypotheses at once", "spawn multiple agents for this bug", "investigate multiple root causes", "parallel hypothesis testing", "parallel investigation", "I can't figure out what's causing this and have a few theories", "investigate from multiple angles", "I have multiple theories about this bug", or reports a complex or intermittent bug where the root cause is unclear and multiple theories need testing simultaneously.
This skill should be used when the user wants to design a new application's architecture or infrastructure — says "design my architecture", "help me plan the architecture", "create architecture diagrams", "I need to plan a new system", or is starting a new project and needs a structured design process. Also trigger when the user mentions HLD, LLD, API contracts, or system design. Guides from requirements gathering through capacity planning, technology selection, diagram generation, low-level design, document saving, and code skeleton implementation.
This skill should be used when the user wants to turn an approved architecture document into working code, or wants to generate/scaffold a project after a design or review session — says "implement the architecture", "scaffold the project", "generate the code from my architecture", "create project files from the design", "turn my architecture into code", "create the folder structure", "start implementation", "let's start coding", or "generate the project skeleton".
This skill should be used when the user wants to review or revise an existing architecture, says "review my architecture", "audit my architecture", "check my architecture", "my architecture needs review", "update my architecture document", "revise the architecture", "architecture drift", "compare design vs implementation", "architecture is outdated", "architecture inconsistency", "check if my code matches my design", or wants to compare their architecture document against their current codebase. Also trigger when the user mentions their architecture document needs updating after new features were added or requirements changed.
This skill should be used when the user invokes /git-helper:generate-commit, or asks to "generate a commit message", "write a commit for me", "what should my commit message be", "help me commit my changes", "suggest a commit message", "prepare a commit", "what commit type should I use", "stage and commit my changes", "commit all my changes", "I'm done working on this", "commit everything I did", "write a commit for my changes", or describes a change they just made and needs a commit message for it. Produces a conventional commit with type, scope, subject, optional body, and breaking change footer.
Apply this skill whenever the user runs /audit, /audit-file, /audit-deps, /audit-report, asks to "review code for security", "check for vulnerabilities", "is this code safe", "audit my dependencies", "scan for CVEs", "find security issues", "OWASP audit", or describes security concerns about their codebase. Also apply whenever the security-auditor agent returns findings that need formatting into a report.
| name | generate-branch |
| description | This skill should be used when the user invokes /git-helper:generate-branch, asks to "create a branch name", "name my branch", "what should I name this branch", "suggest a branch name", "what prefix should I use", "what branch should I create for this", "branch for ticket |
| argument-hint | [work description] |
| allowed-tools | ["Bash","AskUserQuestion"] |
Generate a valid git branch name following team naming conventions. When invoked directly by the user, this skill will ask to create and switch to the branch after generating the name. When invoked via the Skill tool by generate-commit, it outputs the branch name only — the calling skill owns the checkout step.
Collect from the invocation and conversation context:
If no work description is provided, run these commands and infer a 2–5 word description from the staged diff (primary) or unstaged diff (secondary). Append -- <files> to scope diffs to specific paths. Do not ask — infer from diff:
git --no-pager log --oneline -10
git --no-pager status --short
git --no-pager diff [-- <files>]
git --no-pager diff --cached [-- <files>]
If the diff is empty and no description was provided, ask the user for a one-sentence description of the work.
If the description is provided but unclear (e.g., a single ambiguous word like "fix" with no additional context), ask one brief clarifying question before proceeding.
Select prefix — choose the best match; default to feature/ when ambiguous:
| Prefix | When to use |
|---|---|
feature/ | New feature development |
bugfix/ | Non-urgent bug fix |
hotfix/ | Urgent production fix |
release/ | Release preparation (e.g., release/v1.2.0) |
chore/ | Non-code tasks: docs, tooling, config |
bump/ | Dependency/version update |
Build the slug from the work description:
type/scope/slug formatFor the type/scope/slug three-part format and full naming rules, see references/branch-rules.md.
Naming constraints:
| Rule | Valid | Invalid |
|---|---|---|
| Lowercase only | feature/add-login | feature/Add-Login |
| Hyphens as word separator | fix/header-bug | fix/header_bug |
| No special characters | feat/oauth2-login | feat/oauth2@login |
| No consecutive hyphens | feature/new-login | feature/new--login |
| Dots only for version numbers | release/v1.2.0 | feature/new.login |
Present the branch name in a fenced code block, then the ready-to-run command on its own line:
feature/add-oauth2-login
git checkout -b feature/add-oauth2-login
If multiple prefixes are valid, show a primary recommendation and one alternative:
Recommended: bugfix/fix-login-crash
Alternative: hotfix/fix-login-crash ← use this if the fix is urgent
When invoked via the Skill tool by another skill (e.g., generate-commit): always output the branch name in the fenced code block so the calling skill can extract it. Do not ask the user to confirm checkout — the calling skill owns that step.
When invoked directly by the user (not via the Skill tool): after displaying the branch name, use AskUserQuestion to ask:
"Do you want me to create and switch to this branch now?" Options: Yes / No
If the user answers Yes, run git checkout -b <branch-name> immediately and display its output. Do not re-display the command for the user to run — just run it.
If the user answers No, leave the command displayed for the user to run manually.
| User description | Generated branch |
|---|---|
| "Add dark mode toggle to settings" | feature/add-dark-mode-toggle |
| "Fix crash when opening app offline" | bugfix/fix-offline-crash |
| "Urgent: security patch for auth bypass" | hotfix/security-patch-auth-bypass |
| "Prepare v2.0.0 release" | release/v2.0.0 |
| "Update dependencies" | chore/update-dependencies |
| "Bump lodash to 4.17.21" | bump/lodash-4.17.21 |
| "Refactor auth module" (auth scope) | chore/auth/refactor-module |
references/branch-rules.md — Full naming rules with edge cases, regex patterns, and CI/CD compatibility notesscripts/validate-branch.sh — Standalone utility for external/CI use, not invoked as part of this skill's workflow. Validates a branch name against team naming rules. Exit 0 = valid, exit 1 = invalid with reasons listed. Run as: ./scripts/validate-branch.sh <branch-name>