Skip to content

fix: clarify version segment positions in release skill to prevent patch/minor confusion#190

Merged
j4rviscmd merged 3 commits into
mainfrom
fix/fix-release-version-calc
Jun 4, 2026
Merged

fix: clarify version segment positions in release skill to prevent patch/minor confusion#190
j4rviscmd merged 3 commits into
mainfrom
fix/fix-release-version-calc

Conversation

@j4rviscmd
Copy link
Copy Markdown
Owner

Summary

The release skill incorrectly recommended incrementing coderm_minor (segment 5) instead of coderm_patch (segment 6) for patch-level releases. For example, with current version 1.122.0-coderm.0.18.1, a patch release would recommend 1.122.0-coderm.0.19.0 instead of the correct 1.122.0-coderm.0.18.2.

Root Cause

The SKILL.md bash scripts were logically correct, but the AI interpreting the instructions confused which segment to increment. The version format A.B.C-coderm.D.E.F has 6 segments, and the distinction between segment 5 (coderm_minor) and segment 6 (coderm_patch) was not explicit enough.

Changes

  • Added explicit segment position labels ({1}.{2}.{3}-coderm.{4}.{5}.{6}) throughout the release skill
  • Added a mandatory self-verification step (Step 3-3) before AskUserQuestion that requires segment-by-segment comparison
  • Added inline comments in each case branch clarifying which segment is changed
  • Consolidated versioning info into the spec section to reduce duplication
  • Added a "common mistake" example to prevent the exact bug pattern: coderm-patch → 0.19.0 (wrong) vs 0.18.2 (correct)

Test Plan

  • Run the release skill with fix-only changes and verify it recommends incrementing segment 6 only

🤖 Generated with Claude Code

j4rviscmd and others added 3 commits June 2, 2026 23:58
…tch/minor confusion

Add explicit segment position labels (1-6) to version format throughout
the release skill. Add self-verification step before AskUserQuestion
that requires segment-by-segment comparison. Consolidate versioning
info into the spec section to reduce duplication.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@j4rviscmd j4rviscmd added the bug Something isn't working label Jun 4, 2026
@j4rviscmd j4rviscmd merged commit da3d2ef into main Jun 4, 2026
3 checks passed
@j4rviscmd j4rviscmd deleted the fix/fix-release-version-calc branch June 4, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant