specify --version flag not supported, returns error #486
Description
Bug Description
Running specify --version to check the installed version of specify-cli results in an error: No such option: --version. As --version is a standard CLI flag for verifying tool versions, its absence is unexpected and hinders debugging or version verification.
Steps to Reproduce
Install uv on macOS (e.g., via brew install uv or curl -LsSf https://astral.sh/uv/install.sh | sh).
Install specify-cli: uv tool install specify-cli --from git+https://github.com/github/spec-kit.git.
Add /Users/Your_user_name/.local/bin to PATH in ~/.zshrc and run source ~/.zshrc.
Run specify --version.
Observe error: Usage: specify [OPTIONS] COMMAND [ARGS]... Try 'specify --help' for help. No such option: --version.
Expected Behavior
Running specify --version should output the installed version (e.g., specify-cli 0.1.0) or the git commit hash (e.g., abc123).
Actual Behavior
Error: No such option: --version. The help menu (specify --help) lists commands like init and check but offers no alternative for version checking.
Environment
OS: macOS 15.6.1 (Build 24G90)
Shell: zsh
uv version: 0.8.19 (Homebrew 2025-09-19)
specify-cli: Installed from git+https://github.com/github/spec-kit.git (commit unknown due to missing version flag)
Python: 3.8.2
Additional Context
specify --help confirms the CLI is installed and responsive.
Workaround: uv tool list --show-origins shows the commit hash, but it’s less user-friendly than a --version flag.
This issue was encountered while following the Spec Kit manual and videos (https://www.youtube.com/watch?v=a9eR1xsfvHg, https://www.youtube.com/watch?v=Wg-29qf8zR4).
The project’s experimental nature and call for community feedback (e.g., PR #343 for API quotas) suggest this is a valuable usability improvement.
Suggested Fix
Add support for a --version flag to output the CLI version or commit hash.
Alternatively, document an alternative version-checking method (e.g., specify version) in the README or specify --help output.