chore(commands): add /prerelease, update /precommit CHANGELOG step

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: nanotaboada

.claude/commands/precommit.md

@@ -1,8 +1,10 @@
 Run the pre-commit checklist for this project:
 
-1. Remind me to update `CHANGELOG.md` `[Unreleased]` section (Added / Changed / Fixed / Removed) — I must do this manually.
+1. Update `CHANGELOG.md` `[Unreleased]` section — add an entry under the
+   appropriate subsection (Added / Changed / Fixed / Removed) describing the
+   changes made, referencing the issue number.
 2. Run `uv run flake8 .` — must pass.
 3. Run `uv run black --check .` — must pass (run `uv run black .` to auto-fix).
 4. Run `uv run pytest --cov=./ --cov-report=term` — all tests must pass, coverage must be ≥80%.
 
-Run steps 2–4, report the results clearly, then propose a branch name and commit message for my approval using the format `type(scope): description (#issue)` (max 80 chars; types: `feat` `fix` `chore` `docs` `test` `refactor` `ci` `perf`). Do not create the branch or commit until I explicitly confirm.
+Run steps 1–4, report the results clearly, then propose a branch name and commit message for my approval using the format `type(scope): description (#issue)` (max 80 chars; types: `feat` `fix` `chore` `docs` `test` `refactor` `ci` `perf`). Do not create the branch or commit until I explicitly confirm.

.claude/commands/prerelease.md

@@ -0,0 +1,80 @@
+Run the pre-release checklist for this project.
+
+**Working style**: propose before acting at every step — do not commit, push,
+open PRs, or create tags until I explicitly confirm.
+
+---
+
+### Phase 1 — Determine next release
+
+1. **Verify working tree**: Confirm we are on `master` with a clean working
+   tree. Pull latest if behind remote.
+
+2. **Detect current release and propose next**: Read `CHANGELOG.md` for the
+   coach naming convention (A–Z table) and the most recent release heading.
+   Run `git tag --sort=-v:refname` to confirm the latest tag. Then:
+
+   - **Next codename**: next letter in the A–Z sequence after the current one.
+     Use lowercase with no spaces for the tag (e.g. `eriksson`);
+     Title Case for the CHANGELOG heading (e.g. `Eriksson`).
+   - **Version bump** — infer from `[Unreleased]`:
+
+     | Condition | Bump |
+     |---|---|
+     | Any entry marked BREAKING | MAJOR |
+     | Entries under Added | MINOR |
+     | Only Changed / Fixed / Removed | PATCH |
+
+   - If `[Unreleased]` has no entries, stop and warn — there is nothing to release.
+
+   Present a summary before proceeding:
+   ```
+   Current:  v2.1.0-delbosque
+   Proposed: v2.2.0-eriksson  (MINOR — new features in Added)
+   Branch:   release/v2.2.0-eriksson
+   Tag:      v2.2.0-eriksson
+   ```
+
+---
+
+### Phase 2 — Prepare release branch
+
+3. **Create release branch**: `release/vX.Y.Z-{codename}`.
+
+4. **Update CHANGELOG.md**: Move all content under `[Unreleased]` into a new
+   versioned heading `[X.Y.Z - Codename] - {today's date}`. Replace
+   `[Unreleased]` with a fresh empty template:
+
+   ```markdown
+   ## [Unreleased]
+
+   ### Added
+
+   ### Changed
+
+   ### Fixed
+
+   ### Removed
+   ```
+
+5. **Propose commit**: `docs(changelog): release vX.Y.Z Codename`
+
+6. **After confirmation**: commit. Then run steps 2–4 of `/precommit` (linting,
+   formatting, tests — the CHANGELOG step is already handled). Push the branch
+   and open a PR into `master` only once all checks pass.
+
+---
+
+### Phase 3 — Tag and release
+
+7. **Stop and wait** for confirmation that:
+   - All CI checks have passed
+   - CodeRabbit review comments have been addressed
+   - The PR has been merged into `master`
+
+8. **Pull `master`**, then propose the annotated tag:
+   - Tag name: `vX.Y.Z-{codename}`
+   - Message:  `Release X.Y.Z - Codename`
+
+9. **After confirmation**: create and push the tag. The CD pipeline triggers
+   automatically.