Name: generate-branch-name
Author: zacol

Prompt file imported from zacol/happyrisk (.windsurf/workflows/generate-branch-name.md). Copyright stays with the author.

generate-branch-name

Description

Generate a branch name based on current code changes and repository conventions.

Use this workflow when:

You are about to create a new branch
You want consistent branch naming
You follow Conventional Commits-style naming

Instructions

1. Review Commit History

Analyze the last ~10–20 commits
Identify:
- Common prefixes (feat, fix, refactor, etc.)
- Naming patterns

2. Analyze Current Changes

Review:
- Staged changes (git diff --cached)
- Unstaged changes (git diff)
Determine:
- What was changed?
- Why it was changed
- Affected areas

3. Classify the Change Type

Choose:

feat, fix, refactor, docs, style, test, chore, perf

4. Generate Branch Name

Format:

<type>/<short-description>

Rules:

Use kebab-case
Be concise and descriptive
Focus on intent

Examples:

feat/add-user-authentication
fix/login-validation-error
refactor/api-response-handling

Output Format

Branch name:
<generated-branch-name>

Reasoning:
<brief explanation>

{ "prompt": "# generate-branch-name\n\n## Description\n\nGenerate a branch name based on current code changes and repository conventions.\n\nUse this workflow when:\n\n- You are about to create a new branch\n- You want consistent branch naming\n- You follow Conventional Commits-style naming\n\n---\n\n## Instructions\n\n### 1. Review Commit History\n\n- Analyze the last ~10–20 commits\n- Identify:\n - Common prefixes (`feat`, `fix`, `refactor`, etc.)\n - Naming patterns\n\n### 2. Analyze Current Changes\n\n- Review:\n - Staged changes (`git diff --cached`)\n - Unstaged changes (`git diff`)\n- Determine:\n - What was changed?\n - Why it was changed\n - Affected areas\n\n### 3. Classify the Change Type\n\nChoose:\n\n- `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `chore`, `perf`\n\n### 4. Generate Branch Name\n\n**Format:**\n\n```text\n<type>/<short-description>\n```\n\n**Rules:**\n\n- Use kebab-case\n- Be concise and descriptive\n- Focus on intent\n\n**Examples:**\n\n```text\nfeat/add-user-authentication\nfix/login-validation-error\nrefactor/api-response-handling\n```\n\n---\n\n## Output Format\n\n```text\nBranch name:\n<generated-branch-name>\n\nReasoning:\n<brief explanation>\n```", "variables": [], "notes": "Generate a branch name based on current code changes and repository conventions.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/zacol/happyrisk", "path": ".windsurf/workflows/generate-branch-name.md", "ref": "c9c025f8b5ab7916686ed876cc981e02da765d5b", "url": "https://github.com/zacol/happyrisk/blob/c9c025f8b5ab7916686ed876cc981e02da765d5b/.windsurf/workflows/generate-branch-name.md", "key": "zacol/happyrisk/.windsurf/workflows/generate-branch-name.md" } } }

generate-branch-name

About