chore(claude): rename and extend slash commands (#293)

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

Author: nanotaboada

.claude/commands/pre-commit.md

@@ -0,0 +1,11 @@
+Run the pre-commit checklist for this project:
+
+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 `./mvnw clean install` — must succeed with no compilation warnings and all tests passing.
+3. Remind me to open `target/site/jacoco/index.html` to verify coverage after the build completes.
+4. If `coderabbit` CLI is installed, run `coderabbit review --type uncommitted --prompt-only`:
+   - If actionable/serious findings are reported, stop and address them before proposing the commit.
+   - 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–3, report the results clearly, run step 4 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

@@ -0,0 +1,101 @@
+Run the pre-release checklist for this project. Work through all three phases
+in order, pausing for explicit confirmation at each decision point before
+proceeding. Never create a branch, commit, tag, or push without approval.
+
+---
+
+## Phase 1 — Determine next release
+
+1. Run `git status` and confirm the working tree is clean and on `master`.
+   If not, stop and report the problem.
+
+2. Run `git tag --sort=-v:refname` to list existing tags. Identify the most
+   recent tag matching `v*.*.*-*` and extract its club codename.
+
+3. Read the A–Z club table from `CHANGELOG.md` to find the club that follows
+   the last used codename alphabetically. That is the next club.
+
+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 `### Added` subsection has entries → **minor** bump
+   - Otherwise (only `### Changed`, `### Fixed`, `### Removed`) → **patch** bump
+
+5. Compute the next version by applying the bump to the current latest tag's
+   semver (e.g. `v1.0.0-arsenal` + minor → `1.1.0`).
+
+6. Present a summary for confirmation before continuing:
+   - Last tag and club
+   - Next version and club codename
+   - Bump type and the reasoning (what triggered it)
+   - Proposed tag: `vX.Y.Z-{club}`
+   - Proposed branch: `release/vX.Y.Z-{club}`
+
+   **Wait for explicit approval before proceeding to Phase 2.**
+
+---
+
+## Phase 2 — Prepare release branch
+
+1. Create branch `release/vX.Y.Z-{club}` from `master`.
+
+2. Edit `CHANGELOG.md`:
+   - Replace `## [Unreleased]` with `## [X.Y.Z - ClubName] - YYYY-MM-DD`
+     (use today's date; use the club's display name from the table, e.g.
+     "Barcelona", "Chelsea").
+   - Consolidate duplicate subsection headings (e.g. two `### Added` blocks
+     should be merged into one).
+   - Add a new empty `## [Unreleased]` section at the top (above the new
+     versioned heading) with the standard subsections.
+   - Update the compare links at the bottom of the file:
+     - `[unreleased]` → `.../compare/vX.Y.Z-{club}...HEAD`
+     - Add `[X.Y.Z - ClubName]` → `.../compare/v{prev-tag}...vX.Y.Z-{club}`
+
+3. Show the full diff of `CHANGELOG.md` and propose this commit message:
+
+   ```
+   docs(changelog): prepare release notes for vX.Y.Z-{club} (#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."
+
+5. Propose opening a PR from `release/vX.Y.Z-{club}` into `master`.
+   **Wait for explicit approval before opening.**
+
+6. Open the PR with:
+   - Title: `docs(changelog): prepare release notes for vX.Y.Z-{club}`
+   - Body summarising what is included in this release.
+
+---
+
+## Phase 3 — Tag and release
+
+1. Wait — do not proceed until the user confirms:
+   - CI is green
+   - The PR has been merged into `master`
+
+2. Once confirmed, run:
+   ```bash
+   git checkout master && git pull origin master
+   ```
+   and show the resulting `git log --oneline -3`.
+
+3. Propose the annotated tag:
+   ```bash
+   git tag -a vX.Y.Z-{club} -m "Release vX.Y.Z - ClubName"
+   ```
+
+   **Wait for explicit approval before creating the tag.**
+
+4. Create the tag, then propose:
+   ```bash
+   git push origin vX.Y.Z-{club}
+   ```
+
+   **Wait for explicit approval before pushing.** Remind the user that pushing
+   the tag triggers the CD workflow which will build, publish the Docker image,
+   and create the GitHub Release.

.claude/commands/precommit.md

@@ -4,4 +4,4 @@
 
 ## Claude Code
 
-- Run `/precommit` to execute the full pre-commit checklist for this project.
+- Run `/pre-commit` to execute the full pre-commit checklist for this project.