vexscan: Command for Claude Code

Release vexscan

You are releasing a new version of vexscan.

Step 1: Pre-flight checks

Run these sequentially. If any fail, stop immediately and report the failure.

cargo fmt -- --check

cargo clippy -- -D warnings

cargo nextest run

cargo run -- rules test

Then verify the working tree is clean:

git status --porcelain

If there are uncommitted changes, stop and tell the user to commit or stash first.

Step 2: Determine version bump

Read the current version from Cargo.toml (the version = "X.Y.Z" line).

If $ARGUMENTS is patch, minor, or major: use that directly. Skip analysis.

If $ARGUMENTS is empty: analyze the changes since the last git tag to determine the bump type.

git describe --tags --abbrev=0

git log <last-tag>..HEAD --oneline

git diff <last-tag>..HEAD --stat

Read the actual commit diffs if the summary isn't clear enough. Then classify:

• patch — bug fixes, formatting fixes, rule pattern tweaks, doc typos, dependency updates, CI fixes
• minor — new features, new commands, new detection rules, new output formats, new CLI flags, significant refactors that change behavior
• major — breaking CLI changes (removed/renamed flags, changed output format defaults), breaking config file format changes, removed commands

If you determine major: ask the user for confirmation before proceeding. Explain what breaking changes you found.

If patch or minor: tell the user your reasoning in one line and proceed. Example: "Minor bump — new check command and trust store feature since v0.11.0"

Apply the bump:

• patch → increment patch
• minor → increment minor, reset patch to 0
• major → increment major, reset minor and patch to 0

Tell the user: "Releasing vX.Y.Z (was A.B.C)"

Step 3: Bump version

Edit Cargo.toml — update the version = "..." line to the new version.

Then rebuild to update Cargo.lock:

cargo build --release