chore(claude): address pre-commit and pre-release review feedback (#440)

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

Author: nanotaboada

.claude/commands/pre-commit.md

@@ -9,4 +9,4 @@ Run the pre-commit checklist for this project:
    - If only nitpick-level findings, report them and continue to the commit proposal.
    - If `coderabbit` is not installed, skip this step with a note.
 
-Run steps 1–4, report the results clearly, run step 5 if available, 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 run step 5 (CodeRabbit review) if available, 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/pre-release.md

@@ -12,12 +12,19 @@ proceeding. Never create a branch, commit, tag, or push without approval.
 2. Run `git tag --sort=-v:refname` to list existing tags. Identify the most
    recent tag matching `v*.*.*-*` and extract its stadium codename.
 
-3. Read the A–Z stadium table from `CHANGELOG.md` to find the stadium that
-   follows the last used codename alphabetically. That is the next stadium.
+3. Read the A–Z stadium table from `CHANGELOG.md` to find the next stadium:
+   - **No tags yet**: start at `A` (first stadium in the table).
+   - **Normal case**: use the stadium that follows the last used codename
+     alphabetically. If letters were skipped, pick the next after the
+     highest existing codename — do not backfill gaps.
+   - **Last codename is `Z`** (Zentralstadion): the list is finite. Stop and
+     refer to ADR 0012 for guidance on extending or revisiting the convention.
 
 4. Read the `[Unreleased]` section of `CHANGELOG.md` and infer the version
    bump using these rules (applied in order — first match wins):
-   - Any entry contains the word **BREAKING** → **major** bump
+   - Any entry contains the word **BREAKING** (case-insensitive), a
+     `BREAKING CHANGE:` token in a commit footer, or a `!` suffix after
+     the commit type/scope (e.g. `feat!:` or `feat(scope)!:`) → **major** bump
    - Any `### Added` subsection has entries → **minor** bump
    - Otherwise (only `### Changed`, `### Fixed`, `### Removed`) → **patch** bump
 
@@ -53,15 +60,16 @@ proceeding. Never create a branch, commit, tag, or push without approval.
 
 3. Show the full diff of `CHANGELOG.md` and propose this commit message:
 
-   ```
+   ```text
    docs(changelog): prepare release notes for vX.Y.Z-{stadium} (#issue)
    ```
 
    **Wait for explicit approval before committing.**
 
-4. Run `/pre-commit`, skipping step 1 — CHANGELOG was already updated above.
-   Open with: "Skip step 1 — CHANGELOG was already updated as part of this
-   release branch."
+4. Run `/pre-commit`, manually skipping step 1 — do not re-run or re-attempt
+   the CHANGELOG update; it was already completed above. Open with: "Skip
+   step 1 — CHANGELOG was already updated as part of this release branch."
+   Proceed directly with steps 2–5.
 
 5. Propose opening a PR from `release/vX.Y.Z-{stadium}` into `master`.
    **Wait for explicit approval before opening.**
@@ -86,7 +94,7 @@ proceeding. Never create a branch, commit, tag, or push without approval.
 
 3. Propose the annotated tag:
    ```bash
-   git tag -a vX.Y.Z-{stadium} -m "Release vX.Y.Z - StadiumName"
+   git tag -a vX.Y.Z-{stadium} -m "Release X.Y.Z - StadiumName"
    ```
 
    **Wait for explicit approval before creating the tag.**