commit

# Commit ## Planner Entry Stage and commit changes in the primary conversation after the task-defined implementation checks pass. Do not add broad post-commit `/verify` before push by default. Preserve the hook receipt as normal commit evidence. Create a git commit following this project's Conventional Commits convention. These messages are used by git-cliff (`cliff.toml`) to auto-generate changelogs and release notes. PRs are squash-merged, so the PR title becomes the commit on `main` — CI validates it via `pr-title.yml`. ## Available skills - **`/pr-fixup`** — Use after the PR opens only for CI or actionable reviewer findings. ## Format ``` type: lowercase description ``` ## Allowed Types | Type | Use for | In changelog? | |------|---------|---------------| | `feat` | New features | Yes (Features) | | `fix` | Bug fixes | Yes (Bug Fixes) | | `perf` | Performance improvements | Yes (Performance) | | `refactor` | Code refactoring | Yes (Refactoring) | | `docs` | Documentation changes | Yes (Documentation) | | `chore` | Maintenance, deps, configs | No | | `ci` | CI/CD changes | No | | `test` | Test-only changes | No | ## Rules - Subject **must** start with a lowercase letter - Scope is optional: `feat(ui): add dialog` is valid - Include PR/issue number when relevant: `feat: add release notes (#295)` - Breaking changes: add `!` after type: `feat!: remove legacy API` - Keep the first line under 72 characters - **Body lines must be ≤100 characters** (commitlint `body-...