commit

## Conventional Commits Format

```
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

## Title Rules

- ALL LOWERCASE (no capitalization in description)
- <50 characters
- Imperative mood (e.g., "add" not "added")
- No period at end
- Add "!" before ":" for breaking changes (e.g., `feat!:`, `feat(api)!:`)

**Common Types**: `feat`, `fix`, `docs`, `refactor`, `perf`, `test`, `chore`, `build`, `ci`, `style`

## Body Rules (Mandatory)

- **Body is required** - all commits must include bullet points
- Blank line after title
- ≤72 chars/line
- **Bullet points**: use `- ` prefix, start with imperative verb (Add, Remove, Update, Fix)
- **Optional paragraphs**: context before bullets, explanation after bullets

**Valid formats**:
```
# Simple
- Add feature X
- Update component Y

# With explanation
- Add feature X
- Update component Y

This improves performance by 50%.

# With context
Previous implementation caused memory leaks.

- Refactor memory management
- Add cleanup handlers

Resolves memory issues in production.
```

## Footer (Optional)

Blank line after body, then optionally add footers:

- Issue references: `Closes #123`, `Fixes #456`
- Breaking changes: `BREAKING CHANGE: <description>`
- Co-authorship attribution: `Co-Authored-By: Name <email>`

**Example commit message:**
```
feat(auth): add oauth login flow

- Add Google OAuth 2.0 integration
- Implement callback endpoint handler
- Update session management

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
```

## Your Task

1. **Verify configuration exists**: Check if `.claude/git.local.md` exists. If NOT found, invoke `/config-git` to set up project-specific settings.

2. **Perform safety checks** on pending changes:
   - Detect sensitive files (credentials, secrets, .env files)
   - Warn about large files (>1MB) and large commits (>500 lines)
   - Request user confirmation if issues found

3. **Analyze pending changes** to identify coherent logical units of work and i