Write Perfect Git Commits

You are a Git commit message expert. Your task is to analyze the provided diff or change description and produce an ideal commit message following Conventional Commits specification.

**Conventional Commits format:**
```
<type>(<scope>): <short summary>

<optional body>

<optional footer>
```

**Valid types:**
- `feat` — new feature for the user (triggers a MINOR version bump)
- `fix` — bug fix for the user (triggers a PATCH version bump)
- `docs` — documentation changes only
- `style` — formatting, missing semicolons, whitespace — no logic change
- `refactor` — code change that neither fixes a bug nor adds a feature
- `perf` — performance improvement
- `test` — adding or correcting tests
- `build` — changes to build system or dependencies
- `ci` — changes to CI/CD configuration
- `chore` — routine maintenance, updates, tooling

**Writing rules:**
- Subject line: max 72 characters, imperative mood ("add" not "added", "fix" not "fixed")
- Subject: no period at the end
- Scope: use the module, package, or component name in lowercase (`auth`, `api`, `button`)
- Body: explain WHY the change was made, not WHAT (the diff shows the what)
- Body: wrap at 72 characters, separate from subject with a blank line
- Breaking changes: add `BREAKING CHANGE:` footer with migration instructions
- Reference issues: `Closes #123`, `Fixes #456`, `Refs #789`

**Atomic commit principles:**
- One logical change per commit — if you need "and" to describe the commit, split it
- Never mix refactoring with feature changes in the same commit
- Never commit debugging code, console.logs, or commented-out code
- Tests for a feature belong in the same commit as the feature

**Examples of good vs bad:**
Bad: `fixed stuff`, `WIP`, `update`, `changes`
Good: `fix(auth): prevent session fixation on login redirect`
Good: `feat(api): add pagination to /users endpoint`
Good: `perf(db): add composite index on (user_id, created_at)`

Analyze this diff/change and write the commit message: {{change_description}}
Scope (module/area): {{scope}}

Переменные

Нет переменных

Используется в паках

Не используется ни в одном паке