version-check — Claude Code skill: what it does, how to install
Helps decide whether to update Claude Code or hold back on the current build. Evaluates release risks using changelogs and issue trackers.
npx skills add ykdojo/claude-code-tips --skill version-check -a claude-codeWhat version-check does
Claude Code ships updates once or twice a day. Chasing the bleeding edge constantly exposes you to same-day regressions. The npm stable tag is merely a trailing pointer rather than an LTS build. Blindly pinning it is risky.
Inspection relies on real signals. The skill reads the changelog gap, checks recent GitHub bug reports via gh api for reaction clusters, and reads Reddit threads using a DuckDuckGo redirect to avoid bot walls. It also parses modelUsage in test runs. That confirms whether an older CLI build silently restricts the token context window on a newly released model.
Updating methods require care. Running npm install -g against a native installation fails because of the existing symlink in ~/.local/bin/claude. Forcing that command breaks the launcher, so the skill inspects your binary path before suggesting a fix.
What it helps with
- decide whether updating Claude Code right now is safe
- detect regression clusters across recent GitHub bug reports
- inspect changelog differences between installed and latest builds
- verify if your client restricts the model context window
Example prompts for the agent
- Should I update Claude Code today or stay on my current build?
- Check recent GitHub issues to see if the latest Claude Code release is broken.
- Which Claude Code version is safest to pin right now?
How to install version-check
1Skills CLI (Vercel)
npx skills add ykdojo/claude-code-tips --skill version-check -a claude-code2Manually: put the files in place
~/.claude/skills/version-check/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/version-check/
1Skills CLI (Vercel)
npx skills add ykdojo/claude-code-tips --skill version-check -a codex2Manually: put the files in place
.agents/skills/version-check/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ykdojo/claude-code-tips --skill version-check -a cursor2Manually: put the files in place
.cursor/skills/version-check/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ykdojo/claude-code-tips version-check2Manually: put the files in place
.github/skills/version-check/SKILL.md1Skills CLI (Vercel)
npx skills add ykdojo/claude-code-tips --skill version-check -a gemini-cli2Platform CLI
gemini skills install https://github.com/ykdojo/claude-code-tips --path skills/version-checkManually: put the files in place
.devin/skills/version-check/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ykdojo/claude-code-tips --skill version-check -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about version-check
How do I install version-check in Claude Code?
Run npx skills add ykdojo/claude-code-tips --skill version-check -a claude-code. The skill file will be created at ~/.claude/skills/version-check/SKILL.md.
What does version-check do?
It compares your installed Claude Code version with registry dist-tags, scans recent bug clusters, and advises whether to update or stay put.
Why not simply rely on the npm stable tag?
The stable tag trails latest by a handful of releases and does not act as an LTS. Critical bug fixes frequently arrive in latest first while leaving stable unfixed.
