commit-message-generator

# Commit Message Generator

Generate clear, conventional commit messages from git diffs.

## Quick Start

Analyze staged changes and generate message:
```bash
git diff --staged
# Then generate message following conventional commits format
```

## Instructions

### Step 1: Analyze Changes

Review the git diff to understand:
- What files changed
- What functionality was added/modified/removed
- Scope of changes (component, module, feature)
- Breaking changes or deprecations

```bash
git diff --staged
# or for specific files
git diff --staged path/to/file
```

### Step 2: Determine Commit Type

**feat**: New feature
- Adding new functionality
- New user-facing capability
- New API endpoint

**fix**: Bug fix
- Fixing a bug
- Correcting behavior
- Resolving an issue

**docs**: Documentation
- README updates
- Code comments
- API documentation

**style**: Code style
- Formatting changes
- Missing semicolons
- Whitespace changes
- No code logic changes

**refactor**: Code refactoring
- Restructuring code
- No functionality change
- Performance improvements

**test**: Tests
- Adding tests
- Updating tests
- Test infrastructure

**chore**: Maintenance
- Dependency updates
- Build configuration
- CI/CD changes
- Tooling updates

**perf**: Performance
- Performance improvements
- Optimization changes

**ci**: CI/CD
- CI configuration
- Build scripts
- Deployment changes

**build**: Build system
- Build tool changes
- External dependencies

**revert**: Revert
- Reverting previous commit

### Step 3: Identify Scope

Scope indicates what part of codebase changed:
- Component name: `(button)`, `(navbar)`
- Module name: `(auth)`, `(api)`
- Feature area: `(payments)`, `(search)`
- Package name: `(core)`, `(utils)`

Optional but recommended for clarity.

### Step 4: Write Description

**Subject line** (first line):
- Use imperative mood ("add" not "added")
- No period at end
- Max 50-72 characters
- Lowercase after type
- Clear and concise

**Body** (optional, after blank line):
- Ex