Skip to content

Add /pre-release slash command and extend /pre-commit #293

Description

@nanotaboada

Problem

There is no /pre-release slash command for this repo. The release process (determining the next version and club codename, preparing the release branch, updating CHANGELOG.md, tagging) is done manually and is error-prone.

Additionally, step 1 of /pre-commit currently reads:

"Remind me to update CHANGELOG.md [Unreleased] section (Added / Changed / Fixed / Removed) — I must do this manually."

The agent should handle this step, not defer it to the user. A CodeRabbit review step is also missing from the pre-commit flow.

Proposed Solution

  1. Rename .claude/commands/precommit.md to .claude/commands/pre-commit.md.

  2. Update step 1 of .claude/commands/pre-commit.md to:

    Update CHANGELOG.md [Unreleased] section — add an entry under the appropriate subsection (Added / Changed / Fixed / Removed) describing the changes made, referencing the issue number.

  3. Add a CodeRabbit review step to .claude/commands/pre-commit.md after all checks pass: 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.
    • Skip gracefully with a note if the CodeRabbit CLI is not installed.
  4. Add .claude/commands/pre-release.md implementing a three-phase pre-release checklist:

    • Phase 1 — Determine next release: verify clean master, read the historic football club naming convention from CHANGELOG.md (A–Z table), run git tag --sort=-v:refname, infer the version bump from [Unreleased], and present a summary for confirmation before proceeding.
    • Phase 2 — Prepare release branch: create release/vX.Y.Z-{club}, move [Unreleased] content into a versioned heading, propose the docs(changelog) commit, then run /pre-commit and open a PR — all with explicit confirmation at each step.
    • Phase 3 — Tag and release: wait for CI green and PR merged into master; pull master; propose the annotated tag; push only after explicit approval.

Acceptance Criteria

  • .claude/commands/precommit.md renamed to pre-commit.md
  • Step 1 of /pre-commit updates CHANGELOG.md automatically, referencing the issue number
  • /pre-commit runs coderabbit review --type uncommitted --prompt-only after checks pass; blocks on serious findings, continues on nitpicks
  • /pre-release is available and follows the propose-before-acting workflow
  • Correctly reads the club naming convention from CHANGELOG.md
  • Infers the correct version bump from [Unreleased] content

Activity

  1. coderabbitai commented on Apr 2, 2026

    @coderabbitai
    🔗 Related PRs

    #284 - chore(claude): improve Claude Code integration [merged]
    #287 - ci(release): implement named releases with tag-based deployment (#252) [merged]
    #291 - docs(changelog): prepare release notes for v1.0.0-arsenal [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. changed the title [-]feat: implement /prerelease command[/-] [+]Add /prerelease slash command[/+] on Apr 2, 2026
  3. changed the title [-]Add /prerelease slash command[/-] [+]Add /prerelease slash command and extend /precommit[/+] on Apr 4, 2026
  4. changed the title [-]Add /prerelease slash command and extend /precommit[/-] [+]Add /pre-release slash command and extend /pre-commit[/+] on Apr 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions