creating-branch-name

# Branch Creation with Auto-naming

Analyze git changes (commits and uncommitted changes) to determine appropriate branch name, then create the branch.

## Naming Convention

### Format

```
<type>/<description>
```

### Types

| Type | Usage |
|------|-------|
| `feature/` | New feature |
| `fix/` | Bug fix |
| `refactor/` | Refactoring |
| `docs/` | Documentation |
| `style/` | Code style / design |
| `chore/` | Miscellaneous / config |

### Description Rules

- English, concise
- Start with verb (`add-`, `update-`, `remove-`, `fix-`)
- Kebab-case (hyphen-separated)
- Prioritize clarity over brevity

### Examples

```
feature/add-contact-form
fix/spelling-error-in-footer
refactor/user-controller
docs/update-readme
chore/update-dependencies
```

## Workflow

### Step 1: Analyze Changes

Run these commands to understand changes:

```bash
# Check current branch
git branch --show-current

# View uncommitted changes
git status --short

# View diff of uncommitted changes
git diff --stat

# View staged changes
git diff --cached --stat

# View recent commits (if on a feature branch)
git log --oneline -10
```

### Step 2: Determine Type

Based on changes:

| Changes | Type |
|---------|------|
| New files, new functionality | `feature/` |
| Bug corrections | `fix/` |
| Code restructuring without behavior change | `refactor/` |
| README, comments, docs | `docs/` |
| Formatting, CSS | `style/` |
| Config, dependencies, tooling | `chore/` |

### Step 3: Generate Description

1. Identify the **main purpose** of changes
2. Start with a **verb**: add, update, remove, fix, implement, refactor
3. Keep it **short but clear** (2-4 words ideal)
4. Use **kebab-case**

### Step 4: Create Branch

Once you've determined the appropriate branch name:

```bash
git checkout -b <type>/<description>
```

Present the result in this format:

```
Created branch: <type>/<description>

Reason: <brief explanation of why this name fits the changes>
```

## Anti-patterns

Avoid these names:

```
# Too