Agent-Skills.md

Agent Skills: Claude Code version check

Recommend which Claude Code version to run, or whether to update. Use when asked which Claude Code version is best/safe, whether to update now, whether a recent release is buggy, or what changed since the installed version.

UncategorizedID: ykdojo/claude-code-tips/version-check

Repository

ykdojo/claude-code-tips
ykdojoLicense: NOASSERTION
9,063704

Install this agent skill to your local

pnpm dlx add-skill https://github.com/ykdojo/claude-code-tips/tree/HEAD/skills/version-check

Skill Files

Browse the full folder contents for version-check.

Download Skill

Loading file tree…

skills/version-check/SKILL.md

Skill Metadata

Name
version-check
Description
Recommend which Claude Code version to run, or whether to update. Use when asked which Claude Code version is best/safe, whether to update now, whether a recent release is buggy, or what changed since the installed version.

Claude Code version check

The goal is a recommendation: stay put, update, or pin to a specific version. Claude Code ships latest very frequently (often 1-2x/day), so "best version" is a moving target and the answer is usually a range, not a single build.

Heuristics (read first)

  • stable lags latest and is NOT an LTS. The npm stable dist-tag is just a pointer that trails latest by a handful of patch releases. It can even sit behind an important fix release, so "stable" does not mean "most bugs fixed." Don't blindly recommend @stable.
  • Quiet version = good sign. If nobody is complaining about a recent release, that's a positive signal. A loud pile-on about a specific build is the thing to avoid.
  • Version comparisons are the strongest signal. Posts where people compare builds ("X broke Y, rolled back to Z") tell you exactly which release to avoid.
  • Stay ~a day behind the bleeding edge. Avoid a release that's only a few hours old - let others surface same-day regressions first.
  • The real lever is when you update, not stable-vs-latest. Default Claude Code auto-updates to latest constantly, which is how you drift onto a same-day regression.

1. What's installed vs what's published

claude --version
npm view @anthropic-ai/claude-code dist-tags --json

dist-tags shows latest, stable, and next. Compare against the installed version to see how far ahead/behind each pointer is.

Recent releases and their timestamps (to see how fast things are shipping):

npm view @anthropic-ai/claude-code time --json | python3 -c "import sys,json;d=json.load(sys.stdin);print('\n'.join(f'{k}: {v}' for k,v in list(d.items())[-8:]))"

2. Scan the changelog for regressions in the gap

Fetch the changelog and read the entries between the installed version and latest. Look for "Fixed ... regression in X" lines - if a recent build introduced a regression that has not yet been fixed, that's the one to avoid.

curl -sL https://raw.githubusercontent.com/anthropics/claude-code/main/CHANGELOG.md | awk '/## <LATEST>/,/## <INSTALLED>/'

(Substitute the two version numbers.) A release that is mostly "Fixed …" after a noisy one is usually a safe landing spot.

3. Community sentiment (valuable - do this, don't skip it)

GitHub issues (primary - reliable and fetchable)

The most dependable signal. Search recent open bug reports, sorted by reactions, via gh api in a safeclaw container. A version regression shows up as a cluster of high-reaction issues filed right after a release.

docker exec safeclaw-<name> bash -c 'gh api -X GET search/issues \
  -f q="repo:anthropics/claude-code is:issue is:open created:>=<DATE> label:bug" \
  -f sort=reactions -f per_page=25 \
  --jq ".items[] | \"\(.created_at[:10]) +\(.reactions.total_count) c\(.comments) #\(.number) \(.title)\""'

(Set <DATE> to ~3 days before today.) Cross-reference titles against the changelog gap: if a top issue is already addressed by a fix/flag in latest, that build is safer, not riskier. Mostly minor or server-side (API 500/529) issues = quiet release = good sign.

Reddit (secondary - reachable via the DuckDuckGo hop)

r/ClaudeAI version-comparison threads are valuable, but Reddit now hard-blocks every direct automated route - curl (host + container), the WebSearch crawler (denied by user-agent), AND a cold Playwright navigation (network-security challenge page). The reliable way in is the reddit-fetch skill's DuckDuckGo-hop unlock: navigate Playwright to a html.duckduckgo.com/html/?q=site:reddit.com/r/ClaudeAI+... result redirect once, which sets a session cookie, then direct .json navigation works:

https://www.reddit.com/r/ClaudeAI/search.json?q=claude+code+update+broke+OR+regression&restrict_sr=on&sort=new&t=week&limit=25

Apply the heuristics above: a positive or quiet recent-update thread is reassuring; a high-score "X is broken" thread names the build to skip.

4. Recommend

  • If the installed version is in the recent, well-received range and nothing in the gap regressed: stay put, don't chase a release that's only hours old.
  • If there's a known regression in a build, recommend the last good version and npm install -g @anthropic-ai/claude-code@X.Y.Z to pin/rollback.
  • For anyone who's been burned: disable the auto-updater and update deliberately (the repo's setup script does this), rather than religiously tracking @stable.